This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 1 of 1] docs/overview.txt: Provide short mercurial HOWTO


Am 21.05.2010 um 18:27 schrieb Yann E. MORIN:
> So, basically, that paragraph should just read:
> ---8<---
> RESENDING YOUR REEDITED PATCHES:
> 
> Go back to "CONTRIBUTING YOUR PATCHES".
> ---8<---
> 
Yann, All,

thank you for the comments!

A thing I still do not understand but would like to incorporate into the HOWTO:
How does one know if and when the patches were accepted upstream?
Is this noticed by hg automagically?

AFAI understand that staying in sync with upstream while having a nonempty mq patch queue
is done by:
hg qpop -a
hg pull
hg update
hg qpush -a

What happens to the qpush if the cloned upstream repository already contains
some or all of the patches from 
my local queue?
Am I notified, are the already integrated patches skipped or removed,
or is desaster ahead?

Regards
Titus

PS to Yann:
When I execute the hg email command, ancien.enib.fr sometimes bounces
the mail to you with 554 informing me that my patches are spam.
At least it did not like the first Mac OS patch series.
Really a smart MX host ;-)


--
For unsubscribe information see http://sourceware.org/lists.html#faq


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]