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

Re: reducing line crossings in gitk

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jun 16, 2005, 15:05 UTC
Message-ID
<2cfc403205061608053664cc1e@mail.gmail.com>
In-Reply-To
<17073.28667.819809.89026@cargo.ozlabs.ibm.com>
On 6/16/05, Paul Mackerras <paulus@samba.org> wrote:
Show 19 quoted lines
> Jon Seymour writes:
> 
> > Another feature that would be handy is the ability to be able to
> > create tags by pointing to an item and selecting a "create-tag"
> > action. The effect would be to write the SHA1 id into
> > GIT_DIR/refs/tags in the expected way.
> 
> Hmmm, that would create a "direct" tag, not a normal tag, which is
> an object of type "tag" that contains a reference to a commit along
> with some other stuff.
> 
> In general I'd like to keep gitk as purely a viewer.  Ultimately I'll
> probably do a graphical tool for checking stuff in and other
> operations that modify the repository as well, but I think that should
> be a separate tool.
> 
> Regards,
> Paul.
> 

Fair enough... the reason I suggested it is that I use gitk to help me decide how to merge stuff with the mainline. Currently I have to cut and paste the ids of the "interesting" commits into the command line. It would be nice to be able to point directly to an interesting commit and tag it so that I can later get to it from a command line using a name I can remember.

Still, I can quite accept that I have an idiosyncratic way of interacting with git and gitk.

jon.
-- 
homepage: http://www.zeta.org.au/~jon/
blog: http://orwelliantremors.blogspot.com/
Previous: Paul MackerrasNext: Matthias Urlichs
Message 6 of 7 in “reducing line crossings in gitk”
  1. Paul MackerrasJun 11, 2005
  2. Junio C HamanoJun 11, 2005
  3. Paul MackerrasJun 15, 2005
  4. Jon SeymourJun 15, 2005
  5. Paul MackerrasJun 16, 2005
  6. Jon SeymourJun 16, 2005
  7. Matthias UrlichsJun 12, 2005

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.