Date: Thu, 8 May 2014 16:49:45 -0700
From: "W. Trevor King" <wking@tremily.us>
To: Wael Nasreddine <wael.nasreddine@gmail.com>
Subject: Re: Github?
Message-ID: <20140508234945.GW28634@odin.tremily.us>
References:
 <CA+kKtKAw=nEn2dfcvF6++gD5ng+S3T8SLAdVL=Hs=EsvwUg6aw@mail.gmail.com>
	<87iopgkaiz.fsf@nikula.org> <E1WiJsj-0004mz-VK@teckel.deptj.eu>
	<20140508101325.GC23124@vilya.m0g.net>
	<CA+kKtKA8Q5z6Pys9RAumLTiJvmGwWYKGXDkKr9Mh_6ecV-7sdA@mail.gmail.com>
	<874n0zvqrx.fsf@maritornes.cs.unb.ca>
	<CA+kKtKBSP0RYRy6GgEWcqTsAm_CzkN7zJfkjfwAgq8HqoyU+WQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="b6rSbt24+kIAbQdu"
Content-Disposition: inline
In-Reply-To:
 <CA+kKtKBSP0RYRy6GgEWcqTsAm_CzkN7zJfkjfwAgq8HqoyU+WQ@mail.gmail.com>
OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;
	url=http://tremily.us/pubkey.txt
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: notmuch@notmuchmail.org
Precedence: list


--b6rSbt24+kIAbQdu
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 08, 2014 at 11:18:23PM +0000, Wael Nasreddine wrote:
> Well like I said in my first email, if you guys are interested in owning
> and maintaining the GitHub repo it is yours, besides I have not done
> anything with the history I only added one commit which will never confli=
ct
> with upstream unless you add a .Travis.yml file :)

I don't think merge conflicts are the problem here.  If the GitHub
mirror claims to be a mirror but adds an additional commit B:

  -o---o---o---A  notmuch/master
                \
                 B  github/master

Someone who takes the =E2=80=9Cmirror=E2=80=9D claim at face value may use
github/master as the base for some feature:

  -o---o---o---A  notmuch/master
                \
                 B  github/master
                  \
                   C---o---o  some-feature

Now when they submit the patches to this list, they might send a patch
series that drags in B (probably not what the some-feature author
wanted).  Alternatively, they might send a patch series starting with
C and say =E2=80=9Cthis is based on B=E2=80=9D, and anyone who's only follo=
wing the
main repo thinks, =E2=80=9CWhat is B?  I don't have that commit.=E2=80=9D.

You'll also have to continuously rebase github/master to keep A on top
of notmuch/master, which means any feature branches built on
github/master will *also* have to be continuously rebased:

  -o---o---o---A---D  notmuch/master
                    \
                     A'  github/master
                      \
                       B'---o---o  some-feature

Keeping a fork with commits that aren't upstream is fine, and
maintaining a fork with an additional .Travis.yml file will probably
be pretty easy, but calling that fork a mirror is going to cause
needless confusion.

Cheers,
Trevor

--=20
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

--b6rSbt24+kIAbQdu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJTbBgWAAoJEKKfehoaNkbtIA8QAKzc95pEi5Ddcs91KQ/UYkKS
iaqwdAbFRoh2kzJZbpBBzGPhvSyTFHr0eTSXr0o5EVfIdqMc610qtU0GmeRjztzj
o1+gIst9C/JqWXcaxlH3Vqiaf9bbhJ8UtGLjMoGLcc8cudAvF97UG4pual802kND
Q35RDfQ1HJpMuzrQVWI5A4RjL/BB5r66lLO4r8jl1HqmpKIl3kLTJG6kbHVhH2Ap
W19qj0dPO8zBQSKTMbRoDnBlsh1eHrkWP5tINAi5TKFuK+nLeLXw+OAItDCoLpQ7
fX6H4Z8nBs0cehVWVUtjzpruu9jyOyW2/0CFhO3Go0knHfH7kOW6r56CxRwWXewG
k4eMvD58roIGr4Pb3bnBucPClyukondCOt0dV7loUTJLuY2+dpQIj7YnjhTlhqjj
uuBYrx8dPPxpyK0hq1q3ThNJ3Zwg/HtTDo1cYK9XiT16Ah3jfXCX2bppJ/ihL+w+
h9s4HenYhlKRYKmEYvo0tDO5mZ8kUUZcXWi0NP94rDJv3EZjF/1QxJ/ykW1OcxKO
nMqi8JH0dADPPwX/IgjK92H4vJgNhwsVW1v++Uo8HFxR23CdL0e3iy9VmVOtSvIH
awuiII3PfZFFcixpuUCscYhKc5ESrSakA9VVBYzju8S+Ml5VafnVVKrVMi78L/E3
8RA5z6cbJXrSxYxocFt4
=jDKj
-----END PGP SIGNATURE-----

--b6rSbt24+kIAbQdu--