From: Pierre Habouzit <madcoder@debian.org>
To: Geoff Russell <geoffrey.russell@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: tags and patches
Date: Wed, 13 Jun 2007 13:04:01 +0200 [thread overview]
Message-ID: <20070613110401.GG21684@artemis.intersec.eu> (raw)
In-Reply-To: <93c3eada0706130352h3ad6857eie01e1171fdda3991@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Wed, Jun 13, 2007 at 08:22:23PM +0930, Geoff Russell wrote:
> Dear gits,
>
> (I'm on 1.5.0.5)
>
> The last tag made seems to be missing from a patch ... eg.
>
> cd ~ ; mkdir myrepo ; cd myrepo
> git init-db ; echo STUFF > xxx ; git add xxx
> # work, work, work on xxx
> git commit -a
> git tag v1.0
> # work work work on xxx
> # then I clone this repository
> cd /tmp ; git clone ~/myrepo newmyrepo
> # go back and work some more
> cd ~/myrepo
> echo YYY >>xxx
> git commit -a
> git tag v1.1
> # is git commit -a required to commit the tag???
> git format-patch v1.0
> cd /tmp/newmyrepo
> git am ~/myrepo/THEPATCHNAME
> git tag ls
git tag ls is not the proper way to list tags. Afaict there isn't any
yet, except: ls .git/refs/tags/
git tag ls just tagged your HEAD with the name 'ls' which is obviously
not what you meant :)
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-13 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 10:52 tags and patches Geoff Russell
2007-06-13 11:04 ` Pierre Habouzit [this message]
2007-06-13 12:04 ` Geoff Russell
2007-06-13 12:14 ` Johannes Schindelin
2007-06-14 0:15 ` Geoff Russell
2007-06-14 1:03 ` Johannes Schindelin
2007-06-14 2:05 ` Geoff Russell
2007-06-14 2:19 ` Jeff King
2007-06-14 2:50 ` Geoff Russell
2007-06-14 2:31 ` Johannes Schindelin
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=20070613110401.GG21684@artemis.intersec.eu \
--to=madcoder@debian.org \
--cc=geoffrey.russell@gmail.com \
--cc=git@vger.kernel.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).