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

Re: Tool/Scripts - For maintaining different branches on a repo

From
JTJagan Teki <jagannadh.teki@gmail.com>
Date
Jun 27, 2014, 06:27 UTC
Message-ID
<CAD6G_RQ9KpW4i5BPRNrSWmR5oZn0eAZsvM4S_erCXx0+Y7Oj2Q@mail.gmail.com>
In-Reply-To
<20140620223047.GB856079@vauxhall.crustytoothpaste.net>

On Sat, Jun 21, 2014 at 4:00 AM, brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 8 quoted lines
> On Thu, Jun 19, 2014 at 04:18:22PM +0530, Jagan Teki wrote:
>> Hi,
>>
>> I have a single repo with different kinds of branches say 4 branches.
>> Developers will send a patches wrt to specific branch.
>
> I presume here that you're referring to emailed patches, or patches in
> independent files, as opposed to just having branches with commits.
Let me clear my requirement:

I'm using Thunderbird, the tool will pick the patches with _defined_ subject prefix and apply the respective branches as I inputting.

Please let me know if you still have any clarity.
Show 17 quoted lines
>
>> Is there any opensource tool/script that does applying patches/maintaining
>> the branches in repo w/o manual intervention?
>
> If you want something that works with patches specifically, TopGit might
> do what you want.  If what you're looking for is a tool that accepts
> patches and automatically applies them, I'm not aware of one.  It
> shouldn't be terribly difficult to script, though.
>
> If you don't need to deal with patches and can instead deal with git
> repositories, GitLab and Gitorious offer merge requests, which might
> make life easier.  I have heard that GitLab is less painful to set up.
>
> --
> brian m. carlson / brian with sandals: Houston, Texas, US
> +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
> OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
thanks!
-- 
Jagan.
Previous: brian m. carlson
Message 3 of 3 in “Tool/Scripts - For maintaining different branches on a repo”
  1. Jagan TekiJun 19, 2014
  2. brian m. carlsonJun 20, 2014
  3. Jagan TekiJun 27, 2014

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.