From: "Peter Eriksen" <s022018@student.dtu.dk>
To: git@vger.kernel.org
Subject: Re: little conundrum
Date: Thu, 3 Nov 2005 19:10:03 +0100 [thread overview]
Message-ID: <20051103181002.GA26437@bohr.gbar.dtu.dk> (raw)
In-Reply-To: <200511031741.20496.alan@chandlerfamily.org.uk>
On Thu, Nov 03, 2005 at 05:41:20PM +0000, Alan Chandler wrote:
> I have a little problem I am trying to solve. Tried a few things and got
> nowhere, so I thought I would ask here.
>
> I have two directories one of which contains a tree of source code that was an
> original software package that I downloaded. The other contains the result
> of some unfinished - but quite substancial changes that I had made to that
> source code. Since this was some time ago, I don't have any records, but it
> is quite possible that I added and removed quite a few files.
>
> I would like to make myself a git repository that contains at the start, an
> initial commit of the original downloaded source code, and a second commit on
> the top of that that contains the the current state of play after the changes
> I have made.
What I read from this, is that you could do something like (with Git,
but I suppose Cogito is very similar):
]cd original
]git-init-db
]git-add all-the-files
]git-commit -m "Initial import"
]cp -rf ../modified/* .
]git-status
...fix things up adding and deleting files
]git-commit -m "First big change
The point is, I think git-status will tell you about any
modifications you have made by just overwriting the original
tree with the modified one.
Peter
next prev parent reply other threads:[~2005-11-03 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 17:41 little conundrum Alan Chandler
2005-11-03 17:47 ` Johannes Schindelin
2005-11-03 20:57 ` Peter Eriksen
2005-11-03 22:02 ` Alan Chandler
2005-11-04 0:41 ` Johannes Schindelin
2005-11-03 18:10 ` Peter Eriksen [this message]
2005-11-03 18:48 ` Alan Chandler
2005-11-03 19:16 ` Peter Eriksen
2005-11-03 19:30 ` Alan Chandler
2005-11-03 19:36 ` Peter Eriksen
2005-11-03 20:06 ` Petr Baudis
2005-11-03 22:17 ` Alan Chandler
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=20051103181002.GA26437@bohr.gbar.dtu.dk \
--to=s022018@student.dtu.dk \
--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