git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 4, 2006, 12:45 UTC
Message-ID
<e8dnst$pvh$1@sea.gmane.org>
In-Reply-To
<e5bfff550607040503x75b1abdavbbeb80b41a454e7d@mail.gmail.com>
Marco Costalba wrote:
Show 10 quoted lines
> 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".

Show 5 quoted lines
>> 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
Previous: Marco CostalbaNext: Marco Costalba
Message 3 of 5 in “qgit idea: marking refs (heads and tags)”
  1. Jakub NarebskiJul 4, 2006
  2. Marco CostalbaJul 4, 2006
  3. Jakub NarebskiJul 4, 2006
  4. Marco CostalbaJul 6, 2006
  5. Jakub NarebskiJul 7, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.