-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 12/03/2011 12:11 AM, Brian Harring (ferringb) wrote:
> ferringb 11/12/03 00:11:17
>
> Modified: ChangeLog Added:
> pkgcore-0.7.7.1.ebuild Removed: pkgcore-0.7.6.1.ebuild
> pkgcore-0.7.7-r1.ebuild pkgcore-0.7.7.ebuild Log: pull in 0.7.7.1
> with another fix (metadata); punt older versions that have known
> misbehaviours
>
> (Portage version: 2.1.10.39/cvs/Linux x86_64)
>
Why did you erase the entire Changelog?

- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJO2WvUAAoJEPqDWhW0r/LCBNIQAMHSWqSfY2lH7ziAETPj1moI
LSDReW1RF00O+nc2RWaahvv5cjqc8/nx9gkNuxQT4A9VqqZVjU2nz4CZlEI7hv3F
S450lRgMVss/aBWoJFY+u4nBQ1Yq3kVLDYjWTI97OiSfIBH0als2KFcYdweCKE P0
0TbnHTagBHqdcwJ9BvLXeEVVhYwXFbH61E6YOBTnyFCGtB4IeC DNRpebIawZyj8J
ZJfLkIpj9ef/Tj18SJiqdqX60+MQTnWiut1uKO32SmNjk/wDYDJea6/Gim/91g4D
SO1S6XVYg3rFtEP3PGmu4ivpc304YECygIZwYWClR/ujmRb4GVryhXWuEy0gHTWs
VakDMEU3iJPNf4dm/obKPsojw5Kx1/ZhqmCrHTVp/Ni2WEehB0OUmSIgCIxItk4k
bhuvaVTP1/c3kJzChvXYqLBkthItEi4f3tEPMqQafsbApjYnvwcscgJDj+VA C66p
6buwT/uhbKPULMviZO84xtLUKfTmrB5G3zOD4+0+rJpuVRaF/X6c0sMZH04cELQ+
IDF1DCFqZrlp/Qg9ntozFbVgx2+44/k8ab83As7uh7v9RV1o2YnQO/VkezM1+MU/
YTF6M7exolrMguWis3WiwuDajTbjL+1msFzsj9zTFIj+8W8cHf RrALLTWHdMZbFq
mfMh7lKa38Kh2RMjaJtx
=3zlC
-----END PGP SIGNATURE-----

On Sat, Dec 03, 2011 at 12:22:44AM +0000, Markos Chandras wrote:
> On 12/03/2011 12:11 AM, Brian Harring (ferringb) wrote:
> > ferringb 11/12/03 00:11:17
> >
> > Modified: ChangeLog Added:
> > pkgcore-0.7.7.1.ebuild Removed: pkgcore-0.7.6.1.ebuild
> > pkgcore-0.7.7-r1.ebuild pkgcore-0.7.7.ebuild Log: pull in 0.7.7.1
> > with another fix (metadata); punt older versions that have known
> > misbehaviours
> >
> > (Portage version: 2.1.10.39/cvs/Linux x86_64)
> >
> Why did you erase the entire Changelog?

Command history being:

echangelog
# crap, need to redo it
rm ChangeLog
cvs up Changelog
echangelog
repoman commit -m "blah blah blah"

See if you can spot the typo.

Fixing it meanwhile...
~brian

On Fri, 2 Dec 2011 17:15:12 -0800
Brian Harring <ferringb@gmail.com> wrote:

> On Sat, Dec 03, 2011 at 12:22:44AM +0000, Markos Chandras wrote:
> > On 12/03/2011 12:11 AM, Brian Harring (ferringb) wrote:
> > > ferringb 11/12/03 00:11:17
> > >
> > > Modified: ChangeLog Added:
> > > pkgcore-0.7.7.1.ebuild Removed:
> > > pkgcore-0.7.6.1.ebuild pkgcore-0.7.7-r1.ebuild
> > > pkgcore-0.7.7.ebuild Log: pull in 0.7.7.1 with another fix
> > > (metadata); punt older versions that have known misbehaviours
> > >
> > > (Portage version: 2.1.10.39/cvs/Linux x86_64)
> > >
> > Why did you erase the entire Changelog?
>
> Command history being:
>
> echangelog
> # crap, need to redo it
> rm ChangeLog
> cvs up Changelog
> echangelog
> repoman commit -m "blah blah blah"
>
> See if you can spot the typo.

That's what repo-commit was invented for.

And no, the answer is: no. it isn't a typo spotting tool :P.

--
Best regards,
Michał Górny

On Sat, Dec 3, 2011 at 6:45 AM, Brian Harring <ferringb@gmail.com> wrote:
> Command history being:
>
> echangelog
> # crap, need to redo it
> rm ChangeLog
> cvs up Changelog
> echangelog
> repoman commit -m "blah blah blah"
>
> See if you can spot the typo.
>

Next time, use "cvs up"


--
~Nirbheek Chauhan

Gentoo GNOME+Mozilla Team

On Sat, Dec 03, 2011 at 07:29:03AM +0100, Micha?? G??rny wrote:
> On Fri, 2 Dec 2011 17:15:12 -0800
> Brian Harring <ferringb@gmail.com> wrote:
>
> > On Sat, Dec 03, 2011 at 12:22:44AM +0000, Markos Chandras wrote:
> > > On 12/03/2011 12:11 AM, Brian Harring (ferringb) wrote:
> > > > ferringb 11/12/03 00:11:17
> > > >
> > > > Modified: ChangeLog Added:
> > > > pkgcore-0.7.7.1.ebuild Removed:
> > > > pkgcore-0.7.6.1.ebuild pkgcore-0.7.7-r1.ebuild
> > > > pkgcore-0.7.7.ebuild Log: pull in 0.7.7.1 with another fix
> > > > (metadata); punt older versions that have known misbehaviours
> > > >
> > > > (Portage version: 2.1.10.39/cvs/Linux x86_64)
> > > >
> > > Why did you erase the entire Changelog?
> >
> > Command history being:
> >
> > echangelog
> > # crap, need to redo it
> > rm ChangeLog
> > cvs up Changelog
> > echangelog
> > repoman commit -m "blah blah blah"
> >
> > See if you can spot the typo.
>
> That's what repo-commit was invented for.
>
> And no, the answer is: no. it isn't a typo spotting tool :P.

Note repoman commit already honors layout.conf update-changelog, so
repo-commit doesn't offer anything here that repoman already covers.

Relatively recent, but still...
~harring