From: Jon Seymour <jon.seymour@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: reducing line crossings in gitk
Date: Wed, 15 Jun 2005 22:34:34 +1000 [thread overview]
Message-ID: <2cfc40320506150534380bb5f8@mail.gmail.com> (raw)
In-Reply-To: <17072.3723.242985.824999@cargo.ozlabs.ibm.com>
Paul,
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.
Regards,
jon.
next prev parent reply other threads:[~2005-06-15 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 11:47 reducing line crossings in gitk Paul Mackerras
2005-06-11 18:26 ` Junio C Hamano
2005-06-15 11:18 ` Paul Mackerras
2005-06-15 12:34 ` Jon Seymour [this message]
2005-06-16 12:26 ` Paul Mackerras
2005-06-16 15:05 ` Jon Seymour
2005-06-12 14:30 ` Matthias Urlichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cfc40320506150534380bb5f8@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=junkio@cox.net \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).