From: Alexey Shvetsov <alexxy@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Re: overlay move to git
Date: Mon, 23 Feb 2009 13:18:15 +0300 [thread overview]
Message-ID: <200902231318.25035.alexxy@gentoo.org> (raw)
In-Reply-To: <20090223090855.76aac1b2@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
On Понедельник 23 февраля 2009 10:08:55 Flammie Pirinen wrote:
> 2009-02-22, My Th sanoi:
> > There is my work flow with git on Science overlay.
> >
> > >$ git clone git+ssh://git@git.overlays.gentoo.org/proj/sci.git
> > >$ git branch $NAME
> > >$ git checkout $NAME
> >
> > ... edit ...
> >
> > >$ git add $FILES
> > >$ export ECHANGELOG_USER="Your Name <your.name@gentoo.org>"
> > >$ echangelog
> > >$ ebuild *.ebuild digest
> > >$ repoman -p full
> > >$ git add $FILES
> > >$ git status
> > >$ git commit
> > >$ git push --dry-run -v origin HEAD:master
> > >$ git checkout master
> > >$ git pull origin
> > >$ git checkout $NAME
> > >$ git rebase master
> > >$ git push --dry-run -v origin HEAD:master
> > >$ git push -v origin HEAD:master
> > >$ git checkout master
> > >$ git pull origin
> > >$ git branch -d $NAME
>
> I wonder if this short and simple work flow is really all necessary. I
> have to admit I have no prior experience with DVCS’s and in last thread
> when I asked advice no one replied, so I just did something along the
> lines of:
>
> $ git pull
> $ vim
> $ git commit
> $ git push
>
> During my last update. It seemed like it worked though? Will something
> break soon if I continue to use this set of commands? What is the work
> flow for trivial version bump, if so? I would hope that I do not have
> to execute some 22 commands every time I bump my packages from now on.
Better
$ git pull
$ vim
$ echangelog
$ repoman commit
$ git push
--
Alexey 'Alexxy' Shvetsov
Gentoo/KDE
Gentoo/MIPS
Gentoo Team Ru
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-02-23 12:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 14:03 [gentoo-science] Re: overlay move to git Andrey G. Grozin
2009-02-20 15:44 ` Sébastien Fabbro
2009-02-22 19:45 ` My Th
2009-02-23 7:08 ` Flammie Pirinen
2009-02-23 10:18 ` Alexey Shvetsov [this message]
2009-02-23 12:33 ` Justin
2009-02-23 17:53 ` Justin
2009-02-23 19:51 ` Henry Gebhardt
2009-02-23 20:14 ` Justin
2009-02-23 20:52 ` Henry Gebhardt
2009-02-23 20:56 ` Justin
2009-02-23 21:02 ` Justin
2009-02-23 21:23 ` Henry Gebhardt
2009-02-23 22:15 ` Justin
2009-02-23 21:37 ` Benjamin Bannier
2009-02-23 22:16 ` Justin
2009-02-23 19:54 ` My Th
2009-02-28 20:58 ` Yuriy Rusinov
2009-02-23 10:43 ` My Th
-- strict thread matches above, loose matches on Subject: below --
2009-01-08 21:47 [gentoo-science] " Sébastien Fabbro
2009-01-21 12:50 ` [gentoo-science] " Sébastien Fabbro
2009-01-21 17:25 ` Donnie Berkholz
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=200902231318.25035.alexxy@gentoo.org \
--to=alexxy@gentoo.org \
--cc=gentoo-science@lists.gentoo.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