All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Hards <bradh@frogmouth.net>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] KVM call agenda for April 05
Date: Tue, 5 Apr 2011 19:44:41 +1000	[thread overview]
Message-ID: <201104051944.42609.bradh@frogmouth.net> (raw)
In-Reply-To: <21351316-8430-4743-B75C-4299383F7D76@suse.de>

On Tue, 5 Apr 2011 06:29:48 pm Alexander Graf wrote:
> What exactly do you mean by better-practice git setups?
Some projects try to use special features in git. For example, KDE makes use 
of insteadOf and pushInsteadOf to allow checking out from anongit, and 
committing to the main server using a pseudo-URL. 

Should I have some magic git hooks enabled? Automatic use of checker scripts 
or sign-off?

Is there some way to maintain those version change logs I need if I have to 
submit my patch v26?

Brad

  parent reply	other threads:[~2011-04-05  9:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 19:22 KVM call agenda for April 05 Juan Quintela
2011-04-04 19:22 ` [Qemu-devel] " Juan Quintela
2011-04-04 19:59 ` Anthony Liguori
2011-04-04 19:59   ` Anthony Liguori
2011-04-04 20:38   ` Lucas Meneghel Rodrigues
2011-04-04 20:38     ` Lucas Meneghel Rodrigues
2011-04-05  6:01   ` Brad Hards
2011-04-05  8:27     ` Stefan Hajnoczi
2011-04-05  8:29     ` Alexander Graf
2011-04-05  8:42       ` Stefan Hajnoczi
2011-04-05  9:44       ` Brad Hards [this message]
2011-04-05  9:50         ` Alexander Graf
2011-04-05 10:53         ` Stefan Hajnoczi
2011-04-05 12:04           ` Brad Hards
2011-04-05 12:21       ` Brad Hards
2011-04-05 13:14         ` Stefan Hajnoczi
2011-04-05 20:25           ` Peter Maydell
2011-04-05 20:30             ` Anthony Liguori
2011-04-07  9:38               ` Harsh Bora
2011-04-05  9:36   ` Alon Levy
2011-04-05  9:36     ` Alon Levy

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=201104051944.42609.bradh@frogmouth.net \
    --to=bradh@frogmouth.net \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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 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.