From: Michael Shigorin <mike@osdn.org.ua>
To: devel@lists.altlinux.org
Subject: [devel] Fwd: Re: [Kdenlive-devel] move to git ? [OT]
Date: Sun, 5 Apr 2009 21:52:52 +0300
Message-ID: <20090405185252.GA11530@osdn.org.ua> (raw)
Здравствуйте.
Хозяйке на заметку.
----- Forwarded message from Clifford Wolf <clifford/clifford.at> -----
Date: Sun, 8 Mar 2009 00:08:24 +0100
From: Clifford Wolf <clifford/clifford.at>
To: kevin/dotmon.com, For kdenlive developers <kdenlive-devel/lists.sourceforge.net>
Subject: Re: [Kdenlive-devel] move to git ? [OT]
User-Agent: Mutt/1.5.16 (2007-06-09)
Hi,
On Thu, Mar 05, 2009 at 09:02:11AM +0000, Kevin Donnelly wrote:
> On Wednesday 04 March 2009 07:34, Clifford Wolf wrote:
> > btw: I'm using git a lot for projects that actually are in svn or another
> > scm. in this cases I have a local git repository syncing from the projects
> > central scm. there I can play around with different branches use rebase and
> > all the funny git features and finally send patches to the projects mailing
> > lists..
>
> For interest, how exactly do you do this?
for stuff that's upstream in an svn repository I often use git-svn.
but in most cases my starting point is just a tar archive or the ast
release or something alike. in this cases I often start doing modifications
in the plain extracted sources and recognise at a later point that I should
have used an scm to track my changes. Then I'm using a simple shell script
I wrote:
http://svn.clifford.at/tools/trunk/git-kickin.sh
This script is executed in the extraced sources and is passed the original
tar archive as argument. it then creates a .git directory with the content
of the tar archive as initial commit. its a trivial task but it has turned
out to be pretty helpfull to have a script do this job..
yours,
- clifford
--
To understand recursion, you must first understand recursion.
_______________________________________________
Kdenlive-devel mailing list
Kdenlive-devel/lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
----- End forwarded message -----
--
---- WBR, Michael Shigorin <mike@altlinux.ru>
------ Linux.Kiev http://www.linux.kiev.ua/
reply other threads:[~2009-04-05 18:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090405185252.GA11530@osdn.org.ua \
--to=mike@osdn.org.ua \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git