The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
Cc: Jack Howarth <howarth@bromo.msbb.uc.edu>, linux-kernel@vger.kernel.org
Subject: Re: git snapshots (Was: Re: merging branches remotely with git?)
Date: Fri, 25 Jul 2008 12:42:02 +0100	[thread overview]
Message-ID: <1216986122.7098.36.camel@muff> (raw)
In-Reply-To: <20080725112231.GA28411@digi.com>

On Fri, 2008-07-25 at 13:22 +0200, Uwe Kleine-König wrote:
> Hello,
> 
> > ps Which git represents the git patches (like 2.6.26-git11) which are
> > placed as patches on the www.kernel.org web page under the section
> > The latest snapshot for the stable Linux kernel tree is:.
> AFAIK there is no public tree that contains these tags.  But I have a
> little script that creates them.  See below.

Yeah, a public repo on git.kernel.org containing only the snapshot tags
would be immensely useful.

e.g. Fedora rawhide regularly ships snapshots, so it'd be really nice to
be easily look-up what's been merged since a given snapshot:

  $> git-fetch linus
  $> git-fetch snapshot-tags
  $> git-log v2.6.26-git12..linus/master

(That is, assuming the snapshot script couldn't just push the tags to
Linus's repo ...)

Cheers,
Mark.


  reply	other threads:[~2008-07-25 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 17:30 merging branches remotely with git? Jack Howarth
2008-07-24 19:09 ` Daniel Barkalow
2008-07-24 22:48   ` Jack Howarth
2008-07-24 23:10     ` Daniel Barkalow
2008-07-25 11:22     ` git snapshots (Was: Re: merging branches remotely with git?) Uwe Kleine-König
2008-07-25 11:42       ` Mark McLoughlin [this message]
2008-07-25 23:44         ` Jack Howarth
2008-07-26  2:13           ` Bart Trojanowski

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=1216986122.7098.36.camel@muff \
    --to=markmc@redhat.com \
    --cc=Uwe.Kleine-Koenig@digi.com \
    --cc=howarth@bromo.msbb.uc.edu \
    --cc=linux-kernel@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