From: Blu Corater <blu@daga.cl>
To: git <git@vger.kernel.org>
Subject: use case
Date: Mon, 21 Aug 2006 14:23:38 -0400 [thread overview]
Message-ID: <20060821182338.GA21395@daga.cl> (raw)
Hello all.
I've just recently started to put my projects under git, and I have found
a, maybe unusual, use case in which I am not sure how to procede or even
if git is the right tool. Advice from more seasoned users is welcome.
The picture is like this. I've just have to took over the maintenance of a
piece of software which was not kept under scm. The previous developer
used to just hack on the production systems and make a backup once in a
while. No release policy or anything like that. The software runs on
several machines and controls similar but not identical equipment. The
machines should be swapable, therefore the software running should be
identical in all of them and detect the working environment at runtime.
In top of all, my predecesor was fired a few months before I took control
and, in the meantime, people have been doing random modifications to the
software on the production machines to satisfy new requirements, but not
consolidating them, so the present state is slightly divergent and
incompatible versions of the software on each production machine and the
machines are not swapable any more.
My contingency plan, while I manage to refactor the code and establish
a more sane workflow, was to create a git repository on each production
machine, so I can track and audit changes made by random hackers (I have
been unable to convince all of them to ask me to do it instead), and pull
from all of them to a git repository on my develpment machine to produce a
consolidated version.
I am keeping local branches on my devel repo corresponding to each
production machine and pulling from them every time somebody makes a
modification (after commiting on the production machine of course).
The main problem I am facing now is that I have been unable to make an
octopus merge from all the branches to consolidate them. When I do a
"git-pull . branch1 branch2..." git tells me "Unable to find common commit
with 5f83..." where 5f83... is the sha1 of the head commit of the first
branch on the command line. I am merging every branch with my master
branch one by one now, but it is a very time consumming and error prone
process. I would very much like to octopus merge the branches, with all
the conflicts, and then fix the master branch and release a consolidated
version.
Any hints?
--
Blu.
next reply other threads:[~2006-08-21 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 18:23 Blu Corater [this message]
2006-08-21 20:47 ` use case Johannes Schindelin
2006-08-24 0:37 ` Blu
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=20060821182338.GA21395@daga.cl \
--to=blu@daga.cl \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).