From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: [oe-commits] org.oe.dev merge of '709567d645f4e7cbcb5c96f0cf8b99276d2e9318'
Date: Mon, 24 Sep 2007 12:00:18 +0200 [thread overview]
Message-ID: <46F78AB2.10609@student.utwente.nl> (raw)
In-Reply-To: <E1IZk6G-0000Nw-Ca@linuxtogo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
rwhitby commit schreef:
> merge of '709567d645f4e7cbcb5c96f0cf8b99276d2e9318'
> and 'bbea886577d16293379de278796e667a3ca5aac3'
I've been noticing that you are pushing a lot of spurious, unneeded and excessive merges,
please stop doing that, it creates an unnecessary burden on the servers, users and scm
history.
Please read the manual on http://monotone.ca if you have trouble understanding monotone.
Everyone: we have an automerger running on monotone.openembedded.org roughly every 30
minutes, so 95% of the time the 'multiple head' situation will resolve itself.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFG94qyMkyGM64RGpERAuv0AKCrog+L0/kFUl52gNht10h8l3x34gCgiWe1
Oro73h/mmdUHWFPrKe1M684=
=v0pE
-----END PGP SIGNATURE-----
parent reply other threads:[~2007-09-24 10:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1IZk6G-0000Nw-Ca@linuxtogo.org>]
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=46F78AB2.10609@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.