--===============0743588418==
Content-Type: multipart/signed;
  boundary="nextPart4128164.cLFCYpA0sP";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart4128164.cLFCYpA0sP
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

So I'm trying to think of the best way to ensure that kdesvn-build executes=
=20
the right series of commands to ensure that a given branch is downloaded fr=
om=20
a given repository, even if they get switched in the config file, without=20
having to rely on naming schemes, and without interfering with the user's o=
wn=20
development efforts.

This has been helping me to learn git along the way, which is nice.  This i=
s=20
what I've determined so far:

1. It seems to me that it is best to add the repository to use as a "remote=
"=20
in git.  Right now I'm using git remote -v to list all known remotes.  If t=
he=20
repository is listed then kdesvn-build will just use the corresponding remo=
te=20
object.  If the repository is not already known my plan is to add a remote =
for=20
it, basing the name off of the repo URL (i.e. git://qt.gitorious.org/+kde-
developers/qt/kde-qt.git would use kde-qt as a default remote name).  This=
=20
establishes how to refer to the repository in git.

2. Branching is a bit more difficult for me.  I know that a local tracking=
=20
branch much exist to track a remote branch.  My intention is to use git=20
checkout -b to create the local branch if the branch is not already availab=
le.

My questions are:

* Is there an accepted naming scheme for the local tracking branch?  Right =
now=20
I'm just using $remote/$branch for the name but that gives problems with=20
ambiguous references (I may just substitute - for / to make the branch name=
 I=20
think).
* Is there a good way to tell that there is a local tracking branch=20
specifically for a given remote branch?  I'm thinking this will work:

git branch --contains refs/remotes/$remote/$branch

and that if that command outputs any branches, it will be only branches tha=
t=20
are tracking that remote (and not merely predecessors, for instance).  This=
=20
way kdesvn-build could re-use a local tracking branch that's been already=20
created by the user or a previous kdesvn-build run.

3. From there, I'm planning just to use git checkout $localBranch and then =
git=20
pull to verify that local is up-to-date to complete the process.

Anything else I'm missing?

Regards,
 - Michael Pyne

--nextPart4128164.cLFCYpA0sP
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEABECAAYFAkowdaUACgkQqjQYp5Omm0pLNQCggaIlOsFrgMRWc3FCtQR4fVb6
Hh8An2vQ2x7Q4AplOn6pR9kCVC9j/SRo
=911t
-----END PGP SIGNATURE-----

--nextPart4128164.cLFCYpA0sP--

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

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest

--===============0743588418==--