qgit idea: marking refs (heads and tags)

qgit idea: marking refs (heads and tags)

[Jakub Narebski]

One thing I sorely lack in qgit as compared to gitk (and even gitweb[*1*])
is marking commits with refs (heads and tags, marked with different colors
or different shape marker). gitk currently uses markers in short log line
before text of commit summary, gitweb uses markers after (at the end) of
commit log summary. In qgit head commits are marked as such, but not to
which branche they belong[*2*].

And also somewhat (but to much lesser extent) showing explicitely sha1-ids
for commit, parents, tree, referenced object (in tag), to copy'n'paste to
shell.


[*1*] Currently _only_ in summary view IIRC, see e.g.
http://www.kernel.org/git/?p=git/git.git;a=summary
[*2*] gitk has also somewhat expensive "branches that commit belongs to" and
"closest tag(s) that are in lineage of this commit".

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

Re: qgit idea: marking refs (heads and tags)

[Marco Costalba]

On 7/4/06, Jakub Narebski <jnareb@gmail.com> wrote:
> One thing I sorely lack in qgit as compared to gitk (and even gitweb[*1*])
> is marking commits with refs (heads and tags, marked with different colors
> or different shape marker). gitk currently uses markers in short log line
> before text of commit summary, gitweb uses markers after (at the end) of
> commit log summary. In qgit head commits are marked as such, but not to
> which branche they belong[*2*].

Currently you have to select the head and the status bar will show
related information: branch, tag message, etc.

>
> And also somewhat (but to much lesser extent) showing explicitely sha1-ids
> for commit, parents, tree, referenced object (in tag), to copy'n'paste to
> shell.
>

Something as a typical browser "copy selected link" context menu entry?

  Marco

Re: qgit idea: marking refs (heads and tags)

[Jakub Narebski]

Marco Costalba wrote:

> On 7/4/06, Jakub Narebski <jnareb@gmail.com> wrote:
>> One thing I sorely lack in qgit as compared to gitk (and even gitweb[*1*])
>> is marking commits with refs (heads and tags, marked with different colors
>> or different shape marker). gitk currently uses markers in short log line
>> before text of commit summary, gitweb uses markers after (at the end) of
>> commit log summary. In qgit head commits are marked as such, but not to
>> which branche they belong[*2*].
> 
> Currently you have to select the head and the status bar will show
> related information: branch, tag message, etc.

That is step in right direction, but still when viewing history as a whole
I'd like to know which branch is which. Head refs are marked, so it shouldn't
be much work (well, perhaps some on the GUI side) to add, as an option,
head name somewhere (before or after, or even somwehere else) along commit
"subject".

>> And also somewhat (but to much lesser extent) showing explicitely sha1-ids
>> for commit, parents, tree, referenced object (in tag), to copy'n'paste to
>> shell.
> 
> Something as a typical browser "copy selected link" context menu entry?

Yes, "copy sha1 of selected link" would be nice.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

Re: qgit idea: marking refs (heads and tags)

[Marco Costalba]

On 7/4/06, Jakub Narebski <jnareb@gmail.com> wrote:
>
> >> And also somewhat (but to much lesser extent) showing explicitely sha1-ids
> >> for commit, parents, tree, referenced object (in tag), to copy'n'paste to
> >> shell.
> >
> > Something as a typical browser "copy selected link" context menu entry?
>
> Yes, "copy sha1 of selected link" would be nice.
>

Patch pushed to public repo (git.kernel.org/pub/scm/qgit/qgit.git)

   Marco

Re: qgit idea: marking refs (heads and tags)

[Jakub Narebski]

Marco Costalba wrote:

> On 7/4/06, Jakub Narebski <jnareb@gmail.com> wrote:

>>> Something as a typical browser "copy selected link" context menu entry?
>>
>> Yes, "copy sha1 of selected link" would be nice.
>>
> 
> Patch pushed to public repo (git.kernel.org/pub/scm/qgit/qgit.git)

Thanks a lot!

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git