~enan

I am Enan, a CSE graduate and an OSS enthusiast. I use vim and live in the terminal.

Below are some information about me.

  • Languages: C / C++ / Java / Python / JavaScript / R
  • Database: PostgreSQL / MongoDB
  • Interests: Bug hunting and fixing / Pentesting

You can reach me at 3nan.ajmain@gmail.com.

Recent activity

Re: git.sr.ht - show commit numbers in log 4 days ago

From Enan Ajmain to ~sircmpwn/sr.ht-discuss

Ignore this thread. It was supposed to be a response to another email
but I mistakenly removed the angle brackets from in-reply-to address.

-- 
Enan
3nan.ajmain@gmail.com
https://www.github.com/3N4N

GPG Key ID: 448F8D0D0D6DB601566E396CA031EA10A3ECB75D

Re: git.sr.ht - show commit numbers in log 4 days ago

From Enan Ajmain to ~sircmpwn/sr.ht-discuss

It looks like the log page was inspired by the `git log` output. The
hash is shortened; email is cut from author info; date is relative
to current time. But more or less the same `git log`.

How do you know "where relative to the history" you are when you're
using the command line? Using `rev-list --count <hash-ish>` is the way I
know of, but I don't think it can be incorporated in `git log`. How do
you do it?

P.S. Not suggesting it can't be done in the web interface. I was just
curious how you do it in other git interfaces.

-- 
Enan

Re: git.sr.ht - show commit numbers in log 4 days ago

From Enan Ajmain to ~sircmpwn/sr.ht-discuss

It looks like the log page was inspired by the `git log` output. The
hash is shortened; email is cut from author info; date is relative
to current time. But more or less the same `git log`.

How do you know "where relative to the history" you are when you're
using the command line? Using `rev-list --count <hash-ish>` is the way I
know of, but I don't think it can be incorporated in `git log`. How do
you do it?

P.S. Not suggesting it can't be done in the web interface. I was just
curious how you do it in other git interfaces.

-- 
Enan

Commit hash difference for same patch in different copies 6 days ago

From Enan Ajmain to ~sircmpwn/public-inbox

I was fascinated by the idea of `git send-email`, which I learned from
your efforts. Thank you for that. I have been trying to incorporate that
workflow for contributing little patches to open-source projects.
Creating a new fork (in GitHub) just to fix a typo is overkill. And
getting to send the patch without any client or third-party software or
service, just with an email address, is grand.

But I did find a problem with it. The patch when applied doesn't retain
the original commit hash. When editing the email with `--annotate`, it
does show the commit hash, but I can't find it in the sent email. The
problem with a mismatched hash for the same commit is that forked copy
of the code will give conflict when the contributor tries to pull from
upstream (after upstream has applied the patch, with a different commit
hash). I realize it's a small matter and easily fixed. But even so, it

Re: Let user move to source tree of a branch from the log of that branch 25 days ago

From Enan Ajmain to ~sircmpwn/sr.ht-discuss

On Sat, 3 Sep 2022 03:30:15 +0600
Enan Ajmain <3nan.ajmain@gmail.com> wrote:

> I can move from the log to the tree view of the current branch but I
> cannot do the opposite.

I misspoke. It should be the reverse.

Let user move to source tree of a branch from the log of that branch 25 days ago

From Enan Ajmain to ~sircmpwn/sr.ht-discuss

The interface lets me choose a branch from the `refs` tab. Upon
choosing it puts me in the tree view of the selected branch with
another `log` tab on it's right. I can move from the log to the tree
view of the current branch but I cannot do the opposite. If I want to
see the tree view of this branch, I have to go to `refs` tab and select
this branch again.

I guess one can clink on the colored tag of the branch in the log view.
Is that the intended way to do it and why there is no branch-specific
tree button in the branch-specific log tab?