public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
* Updated the GCJ manual on the branch
@ 2002-04-05  6:20 Nic Ferrier
  2002-04-07 22:32 ` Tom Tromey
  0 siblings, 1 reply; 2+ messages in thread
From: Nic Ferrier @ 2002-04-05  6:20 UTC (permalink / raw)
  To: java

I've just updated the gcj manual (with the changes I'd already made on
the head) on the branch.

I hope I did this right, I don't use CVS branches that often.

I patched the branch ChangeLog and the branch gcj.texi.


I presumed that I didn't need approval because the changes had
already been approved on the head.



Nic

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Updated the GCJ manual on the branch
  2002-04-05  6:20 Updated the GCJ manual on the branch Nic Ferrier
@ 2002-04-07 22:32 ` Tom Tromey
  0 siblings, 0 replies; 2+ messages in thread
From: Tom Tromey @ 2002-04-07 22:32 UTC (permalink / raw)
  To: Nic Ferrier; +Cc: java

>>>>> "Nic" == Nic Ferrier <nferrier@tapsellferrier.co.uk> writes:

Nic> I've just updated the gcj manual (with the changes I'd already
Nic> made on the head) on the branch.

Nic> I hope I did this right, I don't use CVS branches that often.

Look good.  Thanks for doing this.

Nic> I presumed that I didn't need approval because the changes had
Nic> already been approved on the head.

Actually, ordinarily the reverse is true: the rules on the branch are
even more strict than the trunk.  For instance pretty soon any commit
to the branch will require Mark's approval -- even the normal gcj
maintainers won't be able to do unapproved commits.

However in this case we needed the change on the branch.  So you did
the right thing.

Tom

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-04-07 21:31 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-05  6:20 Updated the GCJ manual on the branch Nic Ferrier
2002-04-07 22:32 ` Tom Tromey

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 read-only IMAP folder(s) and NNTP newsgroup(s).