public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Tim Moore <timoore@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: frysk git repository (workflow)
Date: Sat, 27 Oct 2007 17:58:00 -0000	[thread overview]
Message-ID: <47237C31.80909@redhat.com> (raw)
In-Reply-To: <4721FF0F.1020807@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sami Wagiaalla wrote:
> If I am working on several tasks what is the recommended work flow.
> 
> Do I create clones for each task I am working on or branches within the
> same clone.
> 
Usually you create branches within one repo and switch between them using git-checkout.
If you need to look at your work in the non-checked out branches you can use git-diff or
git-cat-file. There are some tricks to "check out" a source tree without an associated
repository, but if you really want to have more than one branch checked out, you can clone
your local repository...

It's extremely fast to switch between branches in git. Unfortunately it's not so fast
to rebuild frysk once you've switched :/ though git does take care to only modify files
that are different on the branches.

> Also how do I publish a branch on sourceware; it seems like the branches
> I create
> with git branch foo are local branches. And in that case is it
git push origin sami:refs/heads/sami

> recommended that I
> publish all my scratch branches on sourceware instead of having local
> clones/branches ?
No, you should publish branches that contain work that you want others to check out but
which won't be checked into the master branch imminently.

Tim

- --
Red Hat France SARL, 171 Avenue Georges Clemenceau
92024 Nanterre Cedex, France.
Siret n° 421 199 464 00056
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHI3wxeDhWHdXrDRURAtyiAKCgeP9e8gdLEbsywlFFBH8x6bfCIgCdFuXn
JjezvITKDAMGAPq39OnJKA8=
=3iOn
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-10-27 17:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 17:09 frysk git repository Tim Moore
2007-10-24 17:20 ` Elena Zannoni
2007-10-25  4:50   ` Tim Moore
2007-10-24 19:51 ` Mark Wielaard
2007-10-24 20:05   ` Mark Wielaard
2007-10-25  4:48     ` Tim Moore
2007-10-25 20:10 ` Andrew Cagney
2007-10-26 14:52 ` frysk git repository (workflow) Sami Wagiaalla
2007-10-27 17:58   ` Tim Moore [this message]
2007-10-26 14:59 ` frysk git repository Mark Wielaard
2007-10-26 16:33   ` Tim Moore
2007-10-26 16:57     ` Mark Wielaard
2007-10-26 18:38       ` Sami Wagiaalla
2007-10-29  8:19         ` Mark Wielaard
2007-10-30 17:20           ` Andrew Cagney
2007-10-26 16:35   ` Tim Moore

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=47237C31.80909@redhat.com \
    --to=timoore@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=swagiaal@redhat.com \
    /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 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).