Re: [git-users] how is name-rev determined

2023-03-23 Thread Uwe Brauer
> On Wed, Mar 22, 2023 at 2:37 PM Uwe Brauer wrote: > Yes. "branches/default", and "branches/stable". > Yes. > If it's named "bug-fix" it's created as a bookmark, if it's named > "branches/bug-fix", it's created as a branch. > But since Git has the notion of refspecs, you can choose on the

Re: [git-users] how is name-rev determined

2023-03-22 Thread Felipe Contreras
On Wed, Mar 22, 2023 at 2:37 PM Uwe Brauer wrote: > > >>> "FC" == Felipe Contreras writes: > > > On Thu, Mar 16, 2023 at 3:26 PM Uwe Brauer wrote: > >> > I wrote the equivalent of hg-git for the git world: git-remote-hg [1], > >> > and there exporting named branches works fine. They have the > >

Re: [git-users] how is name-rev determined

2023-03-22 Thread Uwe Brauer
>>> "FC" == Felipe Contreras writes: > On Thu, Mar 16, 2023 at 3:26 PM Uwe Brauer wrote: >> > I wrote the equivalent of hg-git for the git world: git-remote-hg [1], >> > and there exporting named branches works fine. They have the >> > "branches/" prefix and only one head is tracked. >> >> Do y

Re: [git-users] how is name-rev determined

2023-03-22 Thread Felipe Contreras
On Thu, Mar 16, 2023 at 3:26 PM Uwe Brauer wrote: > > I wrote the equivalent of hg-git for the git world: git-remote-hg [1], > > and there exporting named branches works fine. They have the > > "branches/" prefix and only one head is tracked. > > Do you mean exporting named hg branches into git b

Re: [git-users] how is name-rev determined

2023-03-16 Thread Uwe Brauer
> On Sat, Mar 11, 2023 at 1:11 PM Uwe Brauer wrote: > You are a much more positive person than me. I've had countless > discussions with positive reactions who lead to nothing. It seems this > is going to be another one of those. Or just more naive 😉 > After just one reply it has been com

Re: [git-users] how is name-rev determined

2023-03-16 Thread Felipe Contreras
On Sat, Mar 11, 2023 at 1:11 PM Uwe Brauer wrote: > > > On Thu, Mar 9, 2023 at 8:07 PM Felipe Contreras > > wrote: > > > FWIW I updated the patches and sent them to the dev mailing list so > > they stay on the record: > > > https://lore.kernel.org/git/camp44s0cbum1jzyp57ninikwsxg9kugbkdaoozmnen1a

Re: [git-users] how is name-rev determined

2023-03-11 Thread Uwe Brauer
> On Thu, Mar 9, 2023 at 8:07 PM Felipe Contreras > wrote: > FWIW I updated the patches and sent them to the dev mailing list so > they stay on the record: > https://lore.kernel.org/git/camp44s0cbum1jzyp57ninikwsxg9kugbkdaoozmnen1akvg...@mail.gmail.com/T/#t I just skimmed over the thread. It

Re: [git-users] how is name-rev determined

2023-03-11 Thread Uwe Brauer
> On Thu, Mar 9, 2023 at 8:07 PM Felipe Contreras > wrote: > FWIW I updated the patches and sent them to the dev mailing list so > they stay on the record: Thanks! I have not heard anything back from the hg-git guys, at some point they told me they want bookmarks to be more than git branche

Re: [git-users] how is name-rev determined

2023-03-11 Thread Felipe Contreras
On Thu, Mar 9, 2023 at 8:07 PM Felipe Contreras wrote: > > On Wed, Mar 8, 2023 at 2:28 PM Uwe Brauer wrote: > > > > > On Mon, Mar 6, 2023 at 3:03 PM Uwe Brauer wrote: > > And it seems that in > > https://felipec.wordpress.com/2013/08/27/analysis-of-hg-and-git-branches/ > > > > (https://github.c

Re: [git-users] how is name-rev determined

2023-03-09 Thread Felipe Contreras
On Wed, Mar 8, 2023 at 2:28 PM Uwe Brauer wrote: > > > On Mon, Mar 6, 2023 at 3:03 PM Uwe Brauer wrote: > > It's probably never going to be. The point is that you wouldn't need > > named branches if you knew from where a branch started. > > I am a bit confused, in an earlier mail you said > > ,-

Re: [git-users] how is name-rev determined

2023-03-06 Thread Felipe Contreras
On Mon, Mar 6, 2023 at 8:41 AM Uwe Brauer wrote: > > > > On Sat, Mar 4, 2023 at 1:39 AM Uwe Brauer wrote: > > > It's calculated on the fly. > > Ok, that I was afraid of. > > > Weirdly enough, I wrote a blog post [1] about a debate in 2012 > > precisely about the differences between git and mercur

Re: [git-users] how is name-rev determined

2023-03-06 Thread Uwe Brauer
Last try >>> "UB" == Uwe Brauer writes: >> On Sat, Mar 4, 2023 at 1:39 AM Uwe Brauer wrote: >> It's calculated on the fly. Ok, that I was afraid of. > Weirdly enough, I wrote a blog post [1] about a debate in 2012 > precisely about the differences between git and mercurial, and how > `git

Re: [git-users] how is name-rev determined

2023-03-05 Thread Felipe Contreras
On Sat, Mar 4, 2023 at 1:39 AM Uwe Brauer wrote: > However a solution is to use name-rev > > Like this > > git log --graph --color=always --all --since=2years --decorate --pretty | > git name-rev --annotate-stdin | less -R > > And the resulting graph looks, at least for me, close enough to > m

[git-users] how is name-rev determined

2023-03-03 Thread Uwe Brauer
Hi Since I also use mercurial, one thing I am missing in git, when running git log --graph Is a information, which commit belongs to which branch (an information mercurial provides in named branches) However a solution is to use name-rev Like this git log --graph --color=always --all --si