Message-ID: <42090F91.1070100@arbash-meinel.com>
Date: Tue, 08 Feb 2005 13:14:25 -0600
From: John Arbash Meinel <john@arbash-meinel.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
MIME-Version: 1.0
To: Kevin Geiss <kevin@desertsol.com>
References: <45f995752f10f9663c818afbe2496b26@desertsol.com>
In-Reply-To: <45f995752f10f9663c818afbe2496b26@desertsol.com>
Cc: gnu-arch-users@gnu.org, GNU Arch Developers <gnu-arch-dev@lists.seyza.com>
Subject: [GNU-arch-dev] Re: [Gnu-arch-users] how to fix a bad log message?
Precedence: list
Content-Type: multipart/mixed; boundary="===============0744105562=="
Mime-version: 1.0
Sender: gnu-arch-dev-bounces@lists.seyza.com
Errors-To: gnu-arch-dev-bounces@lists.seyza.com
Status: RO
Content-Length: 2721
Lines: 80
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0744105562==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigA416C1B156BD22CDBCAAF9A7"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA416C1B156BD22CDBCAAF9A7
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Kevin Geiss wrote:

> hi all,
>
> I star-merged some stuff from one tree to another, used tla
> log-for-merge to create a log entry, and committed the merge.
>
> then went on to do other stuff.
>
> that's all fine, BUT, I forgot to edit the log created by tla
> log-for-merge before committing, so now when I run 'tla logs -s' I get
> an empty summary message for patch-12! I can see the log-for-merge
> output using tla changelog or tla cat-log, but it's still a bummer.
>
> is there a way I can edit the log message for patch-12? I don't want
> to change anything else, just the log message. (i already have patches
> 13 through 15 committed too, I don't want to change those)
>
> thanks.


Well, if you only want to change it for "tla logs" and don't worry about
"tla revisions", then you *can* just edit the file in
{arch}/cat/cat--branch/cat--branch--version/patch-logs/patch-12

tla logs just outputs the contents of the patch-logs in the current
working directory.
tla revisions connects to the archive and prints the ones out from there.

I don't really like changing patch-logs, but it is possible. As far as
the archive goes, that's a lot more difficult. I won't really describe
how to do it, since you could corrupt your archive by editing it.

John
=:->

PS> For the dev list, the "log" file is just an optimization, could it
be edited without causing problems, as long as you re-generate the
checksums and signatures?


--------------enigA416C1B156BD22CDBCAAF9A7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCCQ+RJdeBCYSNAAMRAkwyAJ41EXthazn4revG1Yp3CdKs08QKBgCfbzWE
gPU9pOi3kMSMQYcIEI9djW0=
=ekBF
-----END PGP SIGNATURE-----

--------------enigA416C1B156BD22CDBCAAF9A7--

--===============0744105562==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnu-arch-dev mailing list
Gnu-arch-dev@lists.seyza.com
http://lists.seyza.com/cgi-bin/mailman/listinfo/gnu-arch-dev

--===============0744105562==--