git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: query: picking dependant commits from a latest tree

From
SHShiraz Hashim <shiraz.hashim@st.com>
Date
Apr 3, 2012, 04:00 UTC
Message-ID
<20120403040001.GQ1766@localhost.localdomain>
In-Reply-To
<4F75DF56.10902@gmail.com>
Hi Neal,
On Sat, Mar 31, 2012 at 12:29:10AM +0800, Neal Kreitzinger wrote:
Show 15 quoted lines
> 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

Previous: Neal KreitzingerNext: Neal Kreitzinger
Message 3 of 4 in “query: picking dependant commits from a latest tree”
  1. Shiraz HashimMar 27, 2012
  2. Neal KreitzingerMar 30, 2012
  3. Shiraz HashimApr 3, 2012
  4. Neal KreitzingerApr 3, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.