[gentoo-science] Re: overlay move to git

[gentoo-science] Re: overlay move to git

[Sébastien Fabbro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday January 08 Sébastien Fabbro wrote:

> We are planning to  switch the science overlay from subversion to
> git.

Switch is done [1].

For users only layman/playman, you might have to resync/readd the
science repo.

For contributors, please read Gentoo git docs [2]. Also the git web site
has many good docs. 

Thanks,

[1] http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git
[2] http://git.overlays.gentoo.org/

- -- 
Sébastien
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkl3GhMACgkQ1ycZbhPLE2A26gCgiMs9JFnmdbzNdyBfGlrcrYcn
O74An3mUZMDD9soPP4BYelrK18oN9Z7h
=yKpG
-----END PGP SIGNATURE-----

Re: [gentoo-science] Re: overlay move to git

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 390 bytes --]

On 12:50 Wed 21 Jan     , Sébastien Fabbro wrote:
> For users only layman/playman, you might have to resync/readd the
> science repo.

Sweet! I'll start moving packages over from my overlay.

I intend to add a package.mask file for use by 
broken/in-development/9999 ebuilds.

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

[gentoo-science] Re: overlay move to git

[Andrey G. Grozin]

Hello,

I am trying to understand how to use the overlay (I mean read-write, 
read-only usage is trivial - via layman). Following

> [2] http://git.overlays.gentoo.org/

I do

grozin@laptop ~/git $ git clone 
git+ssh://git@git.overlays.gentoo.org/science
Initialized empty Git repository in /home/grozin/git/science/.git/
ERROR:gitosis.serve.main:Repository read access denied
fatal: The remote end hung up unexpectedly

as myself (not as root), because my ~/.ssh/ contains id_dsa and id_dsa.pub 
which allow me, e.g., to ssh to dev.gentoo.org. However, as you see, this 
does nor work.

Next I'll want to know how to push new stuff to 
git.overlays.gentoo.org/science. But for now, even cloning does not work 
via git+ssh (layman -a science works OK, but from this repo I'll be 
unable to push stuff back, right?)

Andrey

Re: [gentoo-science] Re: overlay move to git

[Sébastien Fabbro]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday February 20 Andrey G. Grozin wrote:

>
> grozin@laptop ~/git $ git clone 
> git+ssh://git@git.overlays.gentoo.org/science

Instructions were not so clear on the gitweb page.
Try: 
git clone 
git+ssh://git@git.overlays.gentoo.org/proj/sci.git

You should have read/write access.
If you're not familiar with git, see the git web page for good docs.


- -- 
Sébastien
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)

iEYEARECAAYFAkmez9IACgkQ1ycZbhPLE2DnlQCeO7F0wfvr41QAg5Mqzwmx6LAS
4UMAnRBQYZetXswcC03674IzE4/rXgHt
=+vaB
-----END PGP SIGNATURE-----

Re: [gentoo-science] Re: overlay move to git

[My Th]

Hi!

There is my work flow with git on Science overlay.

Create a local copy of science overlay if you have ssh access:
>$ git clone git+ssh://git@git.overlays.gentoo.org/proj/sci.git

Or if you don't have one:
>$ git clone git://git.overlays.gentoo.org/proj/sci.git

Or update existing one:
>$ git pull origin

Create a new branch for work to be committed:
>$ 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

Try to push changes to overlay and check whether there have been changes
to overlay during your work:
>$ git push --dry-run -v origin HEAD:master

If so update master and rebase your branch:
>$ git checkout master
>$ git pull origin
>$ git checkout $NAME
>$ git rebase master

Push your changes, update master and delete your temporary branch:
>$ git push --dry-run -v origin HEAD:master
>$ git push -v origin HEAD:master
>$ git checkout master
>$ git pull origin
>$ git branch -d $NAME

Or format a patch and send via mail to developer (using send-mail or as
an attachment):
>$ git format-patch -1
>$ git send-email --to someone@gentoo.org --suppress-from 0001-yo.patch

Git formatted patches can be applied and pushed to overlay:
>$ git am 0001-your-package.patch
>$ git push --dry-run -v origin HEAD:master
>$ git push -v origin HEAD:master
>$ git checkout master
>$ git pull origin
>$ git branch -d NAME

Command "gitk" can be used to view your git tree graphically. Other
commands which might interest more are: git remote, git rebase.

Git "push origin" can be used only when your local copy has been created
using git+ssh, otherwise full address has to be used or another named
remote has to be created.

Hope it might be useful to somebody.


Cheers,
Reinis

Re: [gentoo-science] Re: overlay move to git

[Flammie Pirinen]

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.

-- 
Flammie, Gentoo Linux Documentation’s Finnish head translator, Finnish 
overlay keeper and more <http://dev.gentoo.org/~flammie>.

Re: [gentoo-science] Re: overlay move to git

[Alexey Shvetsov]

[-- 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 --]

Re: [gentoo-science] Re: overlay move to git

[My Th]

Yes, it can be shortened, but basically it goes along with the same
lines as your work flow and in addition:
- use echangelog to write ChangeLog
- use repoman to check ebuilds
- create temporary branch for easier coping with others commits

The last one (using git rebase) lets avoid master branch merge commits
(like the one in your commit).

I also started to use git just recently (a week ago), so I might do some
unnecessary things or maybe this work flow can be simplified.. If you
see were and how, I would happily take an advice.


Cheers,
Reinis

P , 2009-02-23 09:08 +0200, Flammie Pirinen rakstīja:
> 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.
> 

Re: [gentoo-science] Re: overlay move to git

[Justin]

[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]

Alexey Shvetsov schrieb:
> 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
> 

But whats important from alexxy's solution is, that if you cannot push,
because your HEAD is not up2date than do

git pull --rebase

and not only

git pull


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Justin]

[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]

Justin schrieb:
> Alexey Shvetsov schrieb:
>> 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
>>
> 
> But whats important from alexxy's solution is, that if you cannot push,
> because your HEAD is not up2date than do
> 
> git pull --rebase
> 
> and not only
> 
> git pull
> 

Sorry wasn't alexxys solution, it was from rei4dan.


But I hit some bad thing, I am working alot with branches and noted that
 the .git dir growths and growths, although I removed the branches. Can
I clean this up?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Henry Gebhardt]

On Mon, Feb 23, 2009 at 6:53 PM, Justin <justin@j-schmitz.net> wrote:
> Justin schrieb:
(...)
>
> But I hit some bad thing, I am working alot with branches and noted that
>  the .git dir growths and growths, although I removed the branches. Can
> I clean this up?

Yes! Collect all the garbage with

$ git gc

~Henry

Re: [gentoo-science] Re: overlay move to git

[My Th]

> > But whats important from alexxy's solution is, that if you cannot push,
> > because your HEAD is not up2date than do
> > 
> > git pull --rebase
> > 
> > and not only
> > 
> > git pull
> > 
> 
> Sorry wasn't alexxys solution, it was from rei4dan.
> 
> 
> But I hit some bad thing, I am working alot with branches and noted that
>  the .git dir growths and growths, although I removed the branches. Can
> I clean this up?
> 

Actually "git pull --rebase" was indeed suggested by alexxy on IRC which
might be more efficient in normal cases than my approach (git pull with
subsequent git rebase).

So now it is something like this (without branches):
>$ git clone
... edit ...
>$ git add
>$ export ECHANGELOG_USER="me <me@gentoo.org>"
>$ echangelog
>$ repoman -p full
>$ git add
>$ git commit
>$ git pull --rebase
>$ git push


Cheers,
Reinis

Re: [gentoo-science] Re: overlay move to git

[Justin]

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

Henry Gebhardt schrieb:
> On Mon, Feb 23, 2009 at 6:53 PM, Justin <justin@j-schmitz.net> wrote:
>> Justin schrieb:
> (...)
>> But I hit some bad thing, I am working alot with branches and noted that
>>  the .git dir growths and growths, although I removed the branches. Can
>> I clean this up?
> 
> Yes! Collect all the garbage with
> 
> $ git gc
> 
> ~Henry
> 
but that doesn't really shrink the size.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Henry Gebhardt]

On Mon, Feb 23, 2009 at 9:14 PM, Justin <justin@j-schmitz.net> wrote:
> Henry Gebhardt schrieb:
>> On Mon, Feb 23, 2009 at 6:53 PM, Justin <justin@j-schmitz.net> wrote:
>>> Justin schrieb:
>> (...)
>>> But I hit some bad thing, I am working alot with branches and noted that
>>>  the .git dir growths and growths, although I removed the branches. Can
>>> I clean this up?
>>
>> Yes! Collect all the garbage with
>>
>> $ git gc
>>
>> ~Henry
>>
> but that doesn't really shrink the size.

That's weird. How big is it getting? (Mine is 4.1 MB)

Re: [gentoo-science] Re: overlay move to git

[Justin]

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

Henry Gebhardt schrieb:
> On Mon, Feb 23, 2009 at 9:14 PM, Justin <justin@j-schmitz.net> wrote:
>> Henry Gebhardt schrieb:
>>> On Mon, Feb 23, 2009 at 6:53 PM, Justin <justin@j-schmitz.net> wrote:
>>>> Justin schrieb:
>>> (...)
>>>> But I hit some bad thing, I am working alot with branches and noted that
>>>>  the .git dir growths and growths, although I removed the branches. Can
>>>> I clean this up?
>>> Yes! Collect all the garbage with
>>>
>>> $ git gc
>>>
>>> ~Henry
>>>
>> but that doesn't really shrink the size.
> 
> That's weird. How big is it getting? (Mine is 4.1 MB)
> 
150mb adn it shrinked with git gc --agressive down to 120mb.

What I did was pulling other overlays as branch, doing an filterbranch
and only merging certain thing. perhaps this is something different than
branching the repo itself.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Justin]

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Justin schrieb:
> Henry Gebhardt schrieb:
>> On Mon, Feb 23, 2009 at 9:14 PM, Justin <justin@j-schmitz.net> wrote:
>>> Henry Gebhardt schrieb:
>>>> On Mon, Feb 23, 2009 at 6:53 PM, Justin <justin@j-schmitz.net> wrote:
>>>>> Justin schrieb:
>>>> (...)
>>>>> But I hit some bad thing, I am working alot with branches and noted that
>>>>>  the .git dir growths and growths, although I removed the branches. Can
>>>>> I clean this up?
>>>> Yes! Collect all the garbage with
>>>>
>>>> $ git gc
>>>>
>>>> ~Henry
>>>>
>>> but that doesn't really shrink the size.
>> That's weird. How big is it getting? (Mine is 4.1 MB)
>>
> 150mb adn it shrinked with git gc --agressive down to 120mb.
> 
> What I did was pulling other overlays as branch, doing an filterbranch
> and only merging certain thing. perhaps this is something different than
> branching the repo itself.
> 
and of course deleted the branches afterwards



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Henry Gebhardt]

On Mon, Feb 23, 2009 at 10:02 PM, Justin <justin@j-schmitz.net> wrote:
> Justin schrieb:
>> Henry Gebhardt schrieb:
>>> On Mon, Feb 23, 2009 at 9:14 PM, Justin <justin@j-schmitz.net> wrote:
>>>> Henry Gebhardt schrieb:
>>>>> On Mon, Feb 23, 2009 at 6:53 PM, Justin <justin@j-schmitz.net> wrote:
>>>>>> Justin schrieb:
>>>>> (...)
>>>>>> But I hit some bad thing, I am working alot with branches and noted that
>>>>>>  the .git dir growths and growths, although I removed the branches. Can
>>>>>> I clean this up?
>>>>> Yes! Collect all the garbage with
>>>>>
>>>>> $ git gc
>>>>>
>>>>> ~Henry
>>>>>
>>>> but that doesn't really shrink the size.
>>> That's weird. How big is it getting? (Mine is 4.1 MB)
>>>
>> 150mb adn it shrinked with git gc --agressive down to 120mb.

Now that is indeed a bit excessive.

>>
>> What I did was pulling other overlays as branch, doing an filterbranch
>> and only merging certain thing. perhaps this is something different than
>> branching the repo itself.
>>
> and of course deleted the branches afterwards
>

Hm, I've never used git filter-branch before, but according to the
manpage the original branches are still stored in .git/refs/original,
so git gc wouldn't remove the objects they reference. Also, there
might still be a reference in .git/refs/remotes. (Possibly

$ git branch -a

will show all of them to you (definitely the remote ones).)

Hope that helps.

~Henry

Re: [gentoo-science] Re: overlay move to git

[Benjamin Bannier]

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

Hi,

On Mon, 23 Feb 2009 22:02:06 +0100
Justin <justin@j-schmitz.net> wrote:

> > 150mb adn it shrinked with git gc --agressive down to 120mb.
> > 
> > What I did was pulling other overlays as branch, doing an
> > filterbranch and only merging certain thing. perhaps this is
> > something different than branching the repo itself.
> > 
> and of course deleted the branches afterwards

This can be a bit confusing, but even though these branches are deleted
they are still saved as refs in your repository. Only after a certain
time they get cleaned up by git gc.

Have a look at the configuration section of
  # git help gc

In particular, look at the value of gc.reflogExpire you are currently
using.


Cheers,

Benjamin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Justin]

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Henry Gebhardt wrote:
> On Mon, Feb 23, 2009 at 10:02 PM, Justin <justin@j-schmitz.net> wrote:
>> Justin schrieb:
>>> Henry Gebhardt schrieb:
>>>> On Mon, Feb 23, 2009 at 9:14 PM, Justin <justin@j-schmitz.net> wrote:
>>>>> Henry Gebhardt schrieb:
>>>>>> On Mon, Feb 23, 2009 at 6:53 PM, Justin <justin@j-schmitz.net> wrote:
>>>>>>> Justin schrieb:
>>>>>> (...)
>>>>>>> But I hit some bad thing, I am working alot with branches and noted that
>>>>>>>  the .git dir growths and growths, although I removed the branches. Can
>>>>>>> I clean this up?
>>>>>> Yes! Collect all the garbage with
>>>>>>
>>>>>> $ git gc
>>>>>>
>>>>>> ~Henry
>>>>>>
>>>>> but that doesn't really shrink the size.
>>>> That's weird. How big is it getting? (Mine is 4.1 MB)
>>>>
>>> 150mb adn it shrinked with git gc --agressive down to 120mb.
> 
> Now that is indeed a bit excessive.
> 
>>> What I did was pulling other overlays as branch, doing an filterbranch
>>> and only merging certain thing. perhaps this is something different than
>>> branching the repo itself.
>>>
>> and of course deleted the branches afterwards
>>
> 
> Hm, I've never used git filter-branch before, but according to the
> manpage the original branches are still stored in .git/refs/original,
> so git gc wouldn't remove the objects they reference. Also, there
> might still be a reference in .git/refs/remotes. (Possibly
> 
> $ git branch -a
> 
> will show all of them to you (definitely the remote ones).)
> 
> Hope that helps.
> 
> ~Henry
> 

yeah I deleted all branches, in branch -a there is only the local master
and the the origin/master.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Justin]

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

Benjamin Bannier wrote:
> Hi,
> 
> On Mon, 23 Feb 2009 22:02:06 +0100
> Justin <justin@j-schmitz.net> wrote:
> 
>>> 150mb adn it shrinked with git gc --agressive down to 120mb.
>>>
>>> What I did was pulling other overlays as branch, doing an
>>> filterbranch and only merging certain thing. perhaps this is
>>> something different than branching the repo itself.
>>>
>> and of course deleted the branches afterwards
> 
> This can be a bit confusing, but even though these branches are deleted
> they are still saved as refs in your repository. Only after a certain
> time they get cleaned up by git gc.
> 
> Have a look at the configuration section of
>   # git help gc
> 
> In particular, look at the value of gc.reflogExpire you are currently
> using.
> 
> 
> Cheers,
> 
> Benjamin

Hey thanks,

that will be the solution. I will take a closer look on this.

thnaks justin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-science] Re: overlay move to git

[Yuriy Rusinov]

Hello !

>>$ git clone
> ... edit ...
>>$ git add

Possible better $git add -p, because it allows to interactively see
future changes.

-- 
Best regards,
Sincerely yours,
Yuriy Rusinov.