public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-arch/bzip2: bzip2-1.0.5-r1.ebuild
Date: Wed, 8 Jun 2011 13:01:04 -0400	[thread overview]
Message-ID: <201106081301.05157.vapier@gentoo.org> (raw)
In-Reply-To: <20110608054449.3dd2a49f@pomiocik.lan>

[-- Attachment #1: Type: Text/Plain, Size: 912 bytes --]

On Tuesday, June 07, 2011 23:44:49 Michał Górny wrote:
> On Tue, 7 Jun 2011 17:45:03 -0400 Mike Frysinger wrote:
> > On Tuesday, June 07, 2011 17:36:59 Ciaran McCreesh wrote:
> > > On Tue, 7 Jun 2011 17:35:11 -0400 Mike Frysinger wrote:
> > > > > And yes, it should be automated. I agree. Doesn't change the
> > > > > current situation.
> > > > 
> > > > of course it does.  it makes the current situation irrelevant.
> > > 
> > > Does this mean we should shortly be expecting to see you do the
> > > work to migrate the tree to Git and to automate ChangeLog
> > > generation?
> > 
> > the tree has already been migrated.  automatic ChangeLog generation
> > is trivial to implement, and many many projects already have scripts
> > to do it.
> 
> Including portage's egencache which can generate ChangeLogs from git.
> Just a side note.

very cool ... wasnt aware of that guy, thanks
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-06-08 17:01 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110516033002.207452004F@flycatcher.gentoo.org>
2011-05-16 13:41 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-arch/bzip2: bzip2-1.0.5-r1.ebuild Mark Loeser
2011-05-16 16:18   ` RB
2011-05-16 17:54   ` Kacper Kowalik
2011-05-16 18:19     ` Francisco Blas Izquierdo Riera (klondike)
2011-05-16 18:24       ` Markos Chandras
2011-05-16 19:45         ` Alec Warner
2011-05-16 19:48           ` Mark Loeser
2011-05-16 19:51           ` Markos Chandras
2011-05-16 19:52             ` Ciaran McCreesh
2011-05-16 19:59               ` Markos Chandras
2011-05-16 20:01               ` Dane Smith
2011-06-07 19:53   ` Mike Frysinger
2011-06-07 20:47     ` Dane Smith
2011-06-07 21:09       ` Mike Frysinger
2011-06-07 21:23         ` Dane Smith
2011-06-07 21:35           ` Mike Frysinger
2011-06-07 21:36             ` Ciaran McCreesh
2011-06-07 21:43               ` Alec Warner
2011-06-07 21:45               ` Mike Frysinger
2011-06-08  3:44                 ` Michał Górny
2011-06-08 17:01                   ` Mike Frysinger [this message]
2011-06-07 21:32         ` Matt Turner
2011-06-07 21:47           ` Mike Frysinger
2011-06-07 22:08             ` Matt Turner
2011-06-07 22:24               ` Mike Frysinger
2011-06-07 23:41                 ` Dale
2011-06-08  3:08                   ` Mike Frysinger
2011-06-08  3:45                     ` Dale
2011-06-08 11:17                       ` Duncan
2011-06-08 12:55                         ` Rich Freeman
2011-06-08 17:04                       ` Mike Frysinger
2011-06-08 18:48                         ` Dale
2011-06-08 19:57                         ` Mike Frysinger
2011-06-08  9:27         ` Patrick Lauer
2011-06-08  9:28           ` Dirkjan Ochtman
2011-06-08  9:43             ` Michał Górny
2011-06-08  9:50               ` Patrick Lauer
2011-06-08  9:45             ` Samuli Suominen
2011-06-08 10:17               ` Dirkjan Ochtman
2011-06-08 17:06           ` Mike Frysinger
2011-06-08 17:40             ` Matt Turner
2011-06-08 18:00               ` Mike Frysinger
2011-06-07 21:14       ` Andreas K. Huettel
2011-06-07 21:23         ` Mike Frysinger
2011-06-07 21:09     ` Samuli Suominen
2011-06-07 21:28       ` Matt Turner

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=201106081301.05157.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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