All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shiraz Hashim <shiraz.hashim@st.com>
To: Neal Kreitzinger <nkreitzinger@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	spear-devel <spear-devel@list.st.com>
Subject: Re: query: picking dependant commits from a latest tree
Date: Tue, 3 Apr 2012 09:30:01 +0530	[thread overview]
Message-ID: <20120403040001.GQ1766@localhost.localdomain> (raw)
In-Reply-To: <4F75DF56.10902@gmail.com>

Hi Neal,

On Sat, Mar 31, 2012 at 12:29:10AM +0800, Neal Kreitzinger wrote:
> On 3/27/2012 4:55 AM, Shiraz Hashim wrote:
> >
> > If I try to pick commits from a latest tree for a particular feature
> > then what is the best way to find out all dependant commits.
> >
> > So for example for the commit which I want to pick there are 10 other
> > commits around that file but some affect other files which themselves
> > have several commits which I must apply.
> >
> > Is their a way to do this efficiently ?
> >
> You're assuming all dependencies reside in the same commits or in common 
> files.  If the changes in a commit are dependent on the previous commit 
> and they do not share any of the same files then what you are proposing 
> is not going to catch that.

You are right, but this would perhaps be caught during tests. But in
the first place how can I find dependent commits to pass build test.

--
regards
Shiraz

  reply	other threads:[~2012-04-03  4:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27  9:55 query: picking dependant commits from a latest tree Shiraz Hashim
2012-03-30 16:29 ` Neal Kreitzinger
2012-04-03  4:00   ` Shiraz Hashim [this message]
2012-04-03 16:55     ` Neal Kreitzinger

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=20120403040001.GQ1766@localhost.localdomain \
    --to=shiraz.hashim@st.com \
    --cc=git@vger.kernel.org \
    --cc=nkreitzinger@gmail.com \
    --cc=spear-devel@list.st.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.