git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Petr Baudis <pasky@ucw.cz>
Cc: Chris Wright <chrisw@osdl.org>, Mark Allen <mrallen1@yahoo.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 0/3] cogito spec file updates
Date: Tue, 3 May 2005 16:01:52 -0700	[thread overview]
Message-ID: <20050503230152.GX18917@shell0.pdx.osdl.net> (raw)
In-Reply-To: <20050503214401.GE15995@pasky.ji.cz>

* Petr Baudis (pasky@ucw.cz) wrote:
> I wouldn't accept this neither. If git.spec is already version
> controlled, it should be up-to-date in the version control. Therefore,
> you need to update it at the time of release, not at the time of
> generating the tarball.

*shrug*

Well, it's guaranteed to be one step out of sync, but I'll just keep
doing what I've been doing.  Build rpm after you release, and send
patch ex-post-facto.

thanks,
-chris

  reply	other threads:[~2005-05-03 22:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 21:15 [PATCH] release tarball make targets Mark Allen
2005-05-03 18:28 ` [PATCH 0/3] cogito spec file updates Chris Wright
2005-05-03 18:30   ` [PATCH 1/3] cogito spec file 0.7-1 Chris Wright
2005-05-03 18:32     ` [PATCH 2/3] cogito spec file 0.8-1 Chris Wright
2005-05-03 18:33       ` [PATCH 3/3] cogito spec file 0.8-2 Chris Wright
2005-05-03 19:35   ` [PATCH 0/3] cogito spec file updates Chris Wright
2005-05-03 21:21     ` Petr Baudis
2005-05-03 21:32       ` Chris Wright
2005-05-03 21:44         ` Petr Baudis
2005-05-03 23:01           ` Chris Wright [this message]
2005-05-04 14:38           ` H. Peter Anvin
2005-05-04 14:54             ` Horst von Brand
2005-05-04 15:01               ` H. Peter Anvin
2005-05-04 15:27             ` Chris Wright
2005-05-04  1:00     ` Horst von Brand

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=20050503230152.GX18917@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=mrallen1@yahoo.com \
    --cc=pasky@ucw.cz \
    /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).