libpng.git hosting via sourceforge

[Brandon Casey-2]

Glenn,

I assume you're still using git for managing libpng.
I haven't seen a message saying that the repository has been
posted anywhere though.  Just wanted to let you know that
sourceforge recently enabled support for git.  Since libpng
already is a project there, maybe it would be the easiest
method for providing git access.

Here is the link to the sourceforge sitedoc on the subject
if you are interested:

   http://apps.sourceforge.net/trac/sitedocs/wiki/Git

-brandon


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[glennrp-2]

Thanks.  Yes, I did see that notice a couple of days ago and plan to
make use of it soon.

Glenn

----- Original Message -----
From: "Brandon Casey" <casey@...>
To: "PNG/MNG implementation discussion list" <png-mng-implement@...>
Sent: Friday, March 6, 2009 6:07:08 PM GMT -05:00 US/Canada Eastern
Subject: [png-mng-implement] libpng.git hosting via sourceforge


Glenn,

I assume you're still using git for managing libpng.
I haven't seen a message saying that the repository has been
posted anywhere though.  Just wanted to let you know that
sourceforge recently enabled support for git.  Since libpng
already is a project there, maybe it would be the easiest
method for providing git access.

Here is the link to the sourceforge sitedoc on the subject
if you are interested:

   http://apps.sourceforge.net/trac/sitedocs/wiki/Git

-brandon


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Bob Friesenhahn]

On Fri, 6 Mar 2009, Brandon Casey wrote:
>
> I assume you're still using git for managing libpng.
> I haven't seen a message saying that the repository has been
> posted anywhere though.  Just wanted to let you know that
> sourceforge recently enabled support for git.  Since libpng
> already is a project there, maybe it would be the easiest
> method for providing git access.

I did the work that Glenn needed to have a GIT server but it seems
that he did nothing with it.  And now I hear that his is going to the
Grand Canyon for a week so he is unlikely to do anything with it this
next week either.

What I can say is that 'git.simplesystems.org' responds on port 9418
to GIT requests and that there is a 'libpng.git' available with libpng
files of some vintage.  Maybe it will work for someone who knows the
correct incantation.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Bob Friesenhahn]

On Sat, 7 Mar 2009, Bob Friesenhahn wrote:
>
> What I can say is that 'git.simplesystems.org' responds on port 9418 to GIT
> requests and that there is a 'libpng.git' available with libpng files of some
> vintage.  Maybe it will work for someone who knows the correct incantation.

Ok, I tried

% git clone git://git.simplesystems.org/libpng.git
Initialized empty Git repository in /home/bfriesen/tmp/libpng/.git/
fatal: The remote end hung up unexpectedly
fetch-pack from 'git://git.simplesystems.org/libpng.git' failed.

And checked the system log and see this error message:

   '/serve/git/libpng.git/.git': repository not exported.

So apparently some extra magical step needs to be taken to prepare the
files for use.  The files are just a straight copy of Glenn's
repository.

The files were last worked with on March 26, 2008 so I have forgotten
everything I learned about git since then.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Brandon Casey-3]

On Sat, Mar 7, 2009 at 11:50 PM, Bob Friesenhahn
<bfriesen@...> wrote:

> On Sat, 7 Mar 2009, Bob Friesenhahn wrote:
>>
>> What I can say is that 'git.simplesystems.org' responds on port 9418 to GIT
>> requests and that there is a 'libpng.git' available with libpng files of some
>> vintage.  Maybe it will work for someone who knows the correct incantation.
>
> Ok, I tried
>
> % git clone git://git.simplesystems.org/libpng.git
> Initialized empty Git repository in /home/bfriesen/tmp/libpng/.git/
> fatal: The remote end hung up unexpectedly
> fetch-pack from 'git://git.simplesystems.org/libpng.git' failed.
>
> And checked the system log and see this error message:
>
>   '/serve/git/libpng.git/.git': repository not exported.
>
> So apparently some extra magical step needs to be taken to prepare the
> files for use.  The files are just a straight copy of Glenn's
> repository.

Possibly the 'git-daemon-export-ok' file does not exist.  This is
indeed a magic file
which indicates to git-daemon that the repository should be exported.

Usually, this would do the trick (but see below first):

   touch /serve/git/libpng.git/git-daemon-export-ok

BUT, it looks like the repository above is not a bare repository.  A
bare repository is a
repository without a working directory.  Basically, it is _just_ the
'.git' directory, but usually
named <proj_name>.git.  The reason I think so is because of the path in
your error message above which ends with '.git'.  This is how a
regular repository would
look, like the one you would get after a clone, which is ready for
developing in.  You can tell
the difference by looking in the libpng.git directory.  If the libpng
source files are there,
then it is not a bare repository.

So, maybe the export-ok file needs to be created one directory down,
in the .git directory, like:

   touch /serve/git/libpng.git/.git/git-daemon-export-ok

Or, you can create a bare repository, which I think is the better thing to do.
It's easy to make a bare repository.  Just move the existing
repository out of the
way, and create a bare clone.  Like:

   cd /serve/git/
   mv libpng.git <somewhere>
   git clone --bare <somewhere>/libpng.git libpng.git

Then, create the git-daemon-export-ok file

  touch libpng.git/git-daemon-export-ok

-brandon

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Glenn Randers-Pehrson]

OK, I tried too.  Following SourceForge's documentation I got to the
point of "git push origen master"  and got a bunch of inscrutable
error messages.

shaggy.simplesystems.org> git push origin master
glennrp@...'s password:
error: src refspec master does not match any.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to
'ssh://glennrp@.../gitroot/libpng'
shaggy.simplesystems.org>

If I had gone with the old tarball method I could have had
libpng-1.4.0beta50 out
hours ago, with the memset of the big_rowbuf array.

I'll try again next week when I get back from vacation.  I suspect
I'll be reverting
to the tried-and-true tarball method.

Glenn

On Sun, Mar 8, 2009 at 3:25 PM, Brandon Casey <drafnel@...> wrote:

> On Sat, Mar 7, 2009 at 11:50 PM, Bob Friesenhahn
> <bfriesen@...> wrote:
>> On Sat, 7 Mar 2009, Bob Friesenhahn wrote:
>>>
>>> What I can say is that 'git.simplesystems.org' responds on port 9418 to GIT
>>> requests and that there is a 'libpng.git' available with libpng files of some
>>> vintage.  Maybe it will work for someone who knows the correct incantation.
>>
>> Ok, I tried
>>
>> % git clone git://git.simplesystems.org/libpng.git
>> Initialized empty Git repository in /home/bfriesen/tmp/libpng/.git/
>> fatal: The remote end hung up unexpectedly
>> fetch-pack from 'git://git.simplesystems.org/libpng.git' failed.
>>
>> And checked the system log and see this error message:
>>
>>   '/serve/git/libpng.git/.git': repository not exported.
>>
>> So apparently some extra magical step needs to be taken to prepare the
>> files for use.  The files are just a straight copy of Glenn's
>> repository.
>
> Possibly the 'git-daemon-export-ok' file does not exist.  This is
> indeed a magic file
> which indicates to git-daemon that the repository should be exported.
>
> Usually, this would do the trick (but see below first):
>
>   touch /serve/git/libpng.git/git-daemon-export-ok
>
> BUT, it looks like the repository above is not a bare repository.  A
> bare repository is a
> repository without a working directory.  Basically, it is _just_ the
> '.git' directory, but usually
> named <proj_name>.git.  The reason I think so is because of the path in
> your error message above which ends with '.git'.  This is how a
> regular repository would
> look, like the one you would get after a clone, which is ready for
> developing in.  You can tell
> the difference by looking in the libpng.git directory.  If the libpng
> source files are there,
> then it is not a bare repository.
>
> So, maybe the export-ok file needs to be created one directory down,
> in the .git directory, like:
>
>   touch /serve/git/libpng.git/.git/git-daemon-export-ok
>
> Or, you can create a bare repository, which I think is the better thing to do.
> It's easy to make a bare repository.  Just move the existing
> repository out of the
> way, and create a bare clone.  Like:
>
>   cd /serve/git/
>   mv libpng.git <somewhere>
>   git clone --bare <somewhere>/libpng.git libpng.git
>
> Then, create the git-daemon-export-ok file
>
>  touch libpng.git/git-daemon-export-ok
>
> -brandon
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> png-mng-implement mailing list
> png-mng-implement@...
> https://lists.sourceforge.net/lists/listinfo/png-mng-implement
>

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Glenn Randers-Pehrson]

I didn't do this part, if I was supposed to do it in my shell account
on SourceForge:

Create an empty repository like this:

mkdir PROJECTNAME
cd PROJECTNAME
git init

because I lost shell access months ago when they switched to sftp.  If I was
supposed to do it on my local host, then I did it, or something equivalent.

On Mon, Mar 9, 2009 at 11:01 PM, Glenn Randers-Pehrson
<glennrp@...> wrote:

> OK, I tried too.  Following SourceForge's documentation I got to the
> point of "git push origen master"  and got a bunch of inscrutable
> error messages.
>
> shaggy.simplesystems.org> git push origin master
> glennrp@...'s password:
> error: src refspec master does not match any.
> fatal: The remote end hung up unexpectedly
> error: failed to push some refs to
> 'ssh://glennrp@.../gitroot/libpng'
> shaggy.simplesystems.org>
>
> If I had gone with the old tarball method I could have had
> libpng-1.4.0beta50 out
> hours ago, with the memset of the big_rowbuf array.
>
> I'll try again next week when I get back from vacation.  I suspect
> I'll be reverting
> to the tried-and-true tarball method.
>
> Glenn
>
> On Sun, Mar 8, 2009 at 3:25 PM, Brandon Casey <drafnel@...> wrote:
>> On Sat, Mar 7, 2009 at 11:50 PM, Bob Friesenhahn
>> <bfriesen@...> wrote:
>>> On Sat, 7 Mar 2009, Bob Friesenhahn wrote:
>>>>
>>>> What I can say is that 'git.simplesystems.org' responds on port 9418 to GIT
>>>> requests and that there is a 'libpng.git' available with libpng files of some
>>>> vintage.  Maybe it will work for someone who knows the correct incantation.
>>>
>>> Ok, I tried
>>>
>>> % git clone git://git.simplesystems.org/libpng.git
>>> Initialized empty Git repository in /home/bfriesen/tmp/libpng/.git/
>>> fatal: The remote end hung up unexpectedly
>>> fetch-pack from 'git://git.simplesystems.org/libpng.git' failed.
>>>
>>> And checked the system log and see this error message:
>>>
>>>   '/serve/git/libpng.git/.git': repository not exported.
>>>
>>> So apparently some extra magical step needs to be taken to prepare the
>>> files for use.  The files are just a straight copy of Glenn's
>>> repository.
>>
>> Possibly the 'git-daemon-export-ok' file does not exist.  This is
>> indeed a magic file
>> which indicates to git-daemon that the repository should be exported.
>>
>> Usually, this would do the trick (but see below first):
>>
>>   touch /serve/git/libpng.git/git-daemon-export-ok
>>
>> BUT, it looks like the repository above is not a bare repository.  A
>> bare repository is a
>> repository without a working directory.  Basically, it is _just_ the
>> '.git' directory, but usually
>> named <proj_name>.git.  The reason I think so is because of the path in
>> your error message above which ends with '.git'.  This is how a
>> regular repository would
>> look, like the one you would get after a clone, which is ready for
>> developing in.  You can tell
>> the difference by looking in the libpng.git directory.  If the libpng
>> source files are there,
>> then it is not a bare repository.
>>
>> So, maybe the export-ok file needs to be created one directory down,
>> in the .git directory, like:
>>
>>   touch /serve/git/libpng.git/.git/git-daemon-export-ok
>>
>> Or, you can create a bare repository, which I think is the better thing to do.
>> It's easy to make a bare repository.  Just move the existing
>> repository out of the
>> way, and create a bare clone.  Like:
>>
>>   cd /serve/git/
>>   mv libpng.git <somewhere>
>>   git clone --bare <somewhere>/libpng.git libpng.git
>>
>> Then, create the git-daemon-export-ok file
>>
>>  touch libpng.git/git-daemon-export-ok
>>
>> -brandon
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
>> -Strategies to boost innovation and cut costs with open source participation
>> -Receive a $600 discount off the registration fee with the source code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> png-mng-implement mailing list
>> png-mng-implement@...
>> https://lists.sourceforge.net/lists/listinfo/png-mng-implement
>>
>

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Bob Friesenhahn]

On Mon, 9 Mar 2009, Glenn Randers-Pehrson wrote:

> OK, I tried too.  Following SourceForge's documentation I got to the
> point of "git push origen master"  and got a bunch of inscrutable
> error messages.
>
> shaggy.simplesystems.org> git push origin master
> glennrp@...'s password:
> error: src refspec master does not match any.
> fatal: The remote end hung up unexpectedly
> error: failed to push some refs to
> 'ssh://glennrp@.../gitroot/libpng'
> shaggy.simplesystems.org>

This is not surprising since the server is currently strictly read
only based on discussions from a year ago.  Unless I am missing
something, the git:// protocol is not very secure.  However, you do
have local secure access at simplesystems.org.  People can send you
any patches via email, or changes can be discussed on this list.
When you get back we can discuss if this satisfies your needs.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Bob Friesenhahn]

On Mon, 9 Mar 2009, Bob Friesenhahn wrote:

>> error: failed to push some refs to
>> 'ssh://glennrp@.../gitroot/libpng'
>> shaggy.simplesystems.org>
>
> This is not surprising since the server is currently strictly read
> only based on discussions from a year ago.  Unless I am missing
> something, the git:// protocol is not very secure.  However, you do
> have local secure access at simplesystems.org.  People can send you
> any patches via email, or changes can be discussed on this list.
> When you get back we can discuss if this satisfies your needs.

Clearly I mis-interpreted Glenn's message since I thought that he was
trying to use the server that I set up for him.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Glenn Randers-Pehrson]

It's been nearly a year since I fooled around with Bob's server.  As I
vaguely recall I had
no luck "pushing" to it but could enter the directory and "pull" or "clone" from
my local git repo.  I gave up before figuring out how to do it properly.

Glenn

On Mon, Mar 9, 2009 at 11:46 PM, Bob Friesenhahn
<bfriesen@...> wrote:

> On Mon, 9 Mar 2009, Bob Friesenhahn wrote:
>
>>> error: failed to push some refs to
>>> 'ssh://glennrp@.../gitroot/libpng'
>>> shaggy.simplesystems.org>
>>
>> This is not surprising since the server is currently strictly read
>> only based on discussions from a year ago.  Unless I am missing
>> something, the git:// protocol is not very secure.  However, you do
>> have local secure access at simplesystems.org.  People can send you
>> any patches via email, or changes can be discussed on this list.
>> When you get back we can discuss if this satisfies your needs.
>
> Clearly I mis-interpreted Glenn's message since I thought that he was
> trying to use the server that I set up for him.
>
> Bob
> --
> Bob Friesenhahn
> bfriesen@..., http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
>
> ------------------------------------------------------------------------------
> _______________________________________________
> png-mng-implement mailing list
> png-mng-implement@...
> https://lists.sourceforge.net/lists/listinfo/png-mng-implement
>

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Brandon Casey-3]

On Mon, Mar 9, 2009 at 10:01 PM, Glenn Randers-Pehrson
<glennrp@...> wrote:

> OK, I tried too.  Following SourceForge's documentation I got to the
> point of "git push origen master"  and got a bunch of inscrutable
> error messages.
>
> shaggy.simplesystems.org> git push origin master
> glennrp@...'s password:
> error: src refspec master does not match any.
> fatal: The remote end hung up unexpectedly
> error: failed to push some refs to
> 'ssh://glennrp@.../gitroot/libpng'
> shaggy.simplesystems.org>

'master' is the name of a branch that you want to push to the remote
'origin'.  'master' is the name given to the initial branch in a git
repository, and is commonly used as the main development branch for
projects using git.  So you will see it used a lot.  Your repository
does not have a branch named 'master'.  Your branches are named v00,
v10, v12, and v14.

Try replacing one of these branch names wherever you see the name 'master'.

   git config branch.v12.remote origin
   git config branch.v12.merge refs/heads/v12
   git push origin v12
   etc.

You can push all of your branches at one time, once they are all set up.

   git push origin v00 v10 v12 v14

Plus, you'll want to push the tags that you have created.  Usually you
push each tag explicitly, like:

   git push origin tag v1.2.103

but in this case, I think you _want_ to push all of your tags i.e. you
don't have any private tags that you _don't_ want to push, so you can
just push _all_ tags with the --tags options to 'git push'

   git push origin --tags

> If I had gone with the old tarball method I could have had
> libpng-1.4.0beta50 out
> hours ago, with the memset of the big_rowbuf array.

:) yes that's true.  But will potential libpng developers understand
_why_ you made the changes that you made, 6 months from now?  The real
benefit to using a VCS is the commit log.  The commit log provides a
place to put the justification for each change that is made.  The
'what', as in 'what was changed', can be obtained easily by looking at
a diff from the previous version, but knowing the 'why' is much more
valuable and will hopefully provide information that future developers
can use to avoid repeating a mistake that has already been fixed (for
one thing).

As I mentioned to Bob, I'm looking forward to seeing some of the
wonderful knowledge that is thrown around on this list get into the
commit log.

> I'll try again next week when I get back from vacation.  I suspect
> I'll be reverting
> to the tried-and-true tarball method.

I hope you give it another shot, I'll be here if you need help.

And have a good vacation.

-brandon

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Brandon Casey-3]

On Mon, Mar 9, 2009 at 10:38 PM, Bob Friesenhahn
<bfriesen@...> wrote:

> On Mon, 9 Mar 2009, Glenn Randers-Pehrson wrote:
>
>> OK, I tried too.  Following SourceForge's documentation I got to the
>> point of "git push origen master"  and got a bunch of inscrutable
>> error messages.
>>
>> shaggy.simplesystems.org> git push origin master
>> glennrp@...'s password:
>> error: src refspec master does not match any.
>> fatal: The remote end hung up unexpectedly
>> error: failed to push some refs to
>> 'ssh://glennrp@.../gitroot/libpng'
>> shaggy.simplesystems.org>
>
> This is not surprising since the server is currently strictly read
> only based on discussions from a year ago.  Unless I am missing
> something, the git:// protocol is not very secure.

Right. You don't want to use the git:// protocol to push to the
server.  You want to push over ssh.  I've read your other email about
thinking Glenn was trying to push to your simplesystems.org host.
Glenn should be able to push to your host over ssh too.  He just needs
to set up a named 'remote' in git terms.  This is similar to the
sourceforge instructions.  He'll just have to use a name other than
'origin' since that name has been configured to point to sourceforge.
I'll use the name 'simplesystems', and Glenn can decide whether he
wants something shorter like 'ss'.

   git remote add simplesystems
ssh://USERNAME@.../git/libpng.git

then

  git fetch simplesystems

which will update your remote tracking branches which can be seen by doing:;

   git branch -r

and to push, just do

   git push simplesystems

Hopefully it is clear what that ssh URL is.  USERNAME of course needs
to be replaced, and if git.simplesystems.org is not the hostname that
you ssh to, then it needs to be corrected.

Also, git and the handful of other git helpers needs to be in your
path since they will be used to update the remote repository over ssh
when pushing.

> However, you do
> have local secure access at simplesystems.org.  People can send you
> any patches via email, or changes can be discussed on this list.

Right, but if Glenn wants to apply the patches and do testing on his
personal machine, it will probably be convenient to then just push the
tested result to simplesystems.

btw, I think it is a good idea to push to both simplesystems and
sourceforge.  It will provide two distribution points and two backups.

-brandon

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Brandon Casey-3]

On Tue, Mar 10, 2009 at 1:19 AM, Brandon Casey <drafnel@...> wrote:

> Try replacing one of these branch names wherever you see the name 'master'.
>
>   git config branch.v12.remote origin
>   git config branch.v12.merge refs/heads/v12
>   git push origin v12
>   etc.
>
> You can push all of your branches at one time, once they are all set up.
>
>   git push origin v00 v10 v12 v14

I misspoke a little here.  You can push a branch with the above
command line at any time.  I said ;"...once they are all set up", but
you don't have to associate a remote with it, or set up the branch for
merging first.

i.e. you can do this:

   git push origin v00 v10 v12 v14

before you do this

   git config branch.v12.remote origin
   git config branch.v12.merge refs/heads/v12
   git config branch.v10.remote origin
   etc.

-brandon

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Bob Friesenhahn]

On Tue, 10 Mar 2009, Brandon Casey wrote:

> I'll use the name 'simplesystems', and Glenn can decide whether he
> wants something shorter like 'ss'.
>
>   git remote add simplesystems
> ssh://USERNAME@.../git/libpng.git
>
>
>> However, you do have local secure access at simplesystems.org.
>>  People can send you any patches via email, or changes can be
>> discussed on this list.
>
> Right, but if Glenn wants to apply the patches and do testing on his
> personal machine, it will probably be convenient to then just push the
> tested result to simplesystems.

Glenn already has the necessary secure SSH access and can use it as
you describe if he chooses to.

> btw, I think it is a good idea to push to both simplesystems and
> sourceforge.  It will provide two distribution points and two backups.

Even if both repository copies end up being identical, there
ultimately should be only one current "master".  It is up to the
maintainer to keep the secondary in sync.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
------------------------------------------------------------------------------

_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[John Bowler]

From: Bob Friesenhahn [mailto:bfriesen@...]
>Even if both repository copies end up being identical, there
>ultimately should be only one current "master".  It is up
>to the maintainer to keep the secondary in sync.

It's much safer if everything is truly distributed, though I don't know if
git supports that.  In a distributed system all repos are equal and there
are only very short periods of time when a given change only exists in one
place.  Loss of repos is harmless - indeed every single repo has to be lost
to create a disaster.

If there is a single master users will naturally go to that - why use a
second class copy?  If the master is lost it's necessary to worry whether
the copies were up to date and validate the newly created master.

John Bowler <jbowler@...>



------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Brandon Casey-2]

John Bowler wrote:

> From: Bob Friesenhahn [mailto:bfriesen@...]
>> Even if both repository copies end up being identical, there
>> ultimately should be only one current "master".  It is up
>> to the maintainer to keep the secondary in sync.
>
> It's much safer if everything is truly distributed, though I don't know if
> git supports that.  In a distributed system all repos are equal and there
> are only very short periods of time when a given change only exists in one
> place.  Loss of repos is harmless - indeed every single repo has to be lost
> to create a disaster.

If I understand you correctly, then yes git supports that.  Every git clone
contains the entire repository history.

> If there is a single master users will naturally go to that - why use a
> second class copy?  If the master is lost it's necessary to worry whether
> the copies were up to date and validate the newly created master.

You're talking about a non-distributed VCS here?  Right, I agree.  Backups
would be made periodically, but if the master repository is lost, the backups
may not have the latest changes committed to the master.

But, as you mention, in the distributed VCS case, all clones are equal, so
losing one is not a big deal.

Side Note:
Another way that I see sourceforge as complementing simplesystems, is that
you get the gitweb features for free.  This allows someone to explore the
source tree and revision history without having to know how to use git.

-brandon

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[John Bowler]

From: Brandon Casey [mailto:casey@...]
>But, as you mention, in the distributed VCS case, all clones are equal, so
>losing one is not a big deal.

That's true of monotone (for example) where the repos effectively form a
network and all repos are equal.  With BitKeeper, as I remember it, there
was a hierarchy in that changes were pushed 'up' and, IRC, it wasn't
possible to connect to a peer repository - one developer had to push changes
up before another could pull them down.

I guess I would say that BitKeeper allows distributed development but isn't
a true distributed VCS, unlike monotone and, presumably, git.  There really
can't be a master repository with monotone - the concept doesn't have any
natural interpretation.

John Bowler <jbowler@...>



------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Bob Friesenhahn]

On Tue, 10 Mar 2009, Brandon Casey wrote:
>
> You're talking about a non-distributed VCS here?  Right, I agree.  Backups
> would be made periodically, but if the master repository is lost, the backups
> may not have the latest changes committed to the master.
>
> But, as you mention, in the distributed VCS case, all clones are equal, so
> losing one is not a big deal.

It is not possible to have a distributed VCS, with all clones being
completely equal, unless they use a database-like transaction
architecture.  This requires that all of the clones are accessible at
once, which is not necessarily possible.

> Another way that I see sourceforge as complementing simplesystems, is that
> you get the gitweb features for free.  This allows someone to explore the
> source tree and revision history without having to know how to use git.

Presumably I can also provide this gitweb capability.  I already
provide CVSWeb, and it is relatively easy.

Regardless, having several trusted repositories is a good idea.
Someday SourceForge or my little site may abruptly be gone.
SourceForge is a business and like any other struggling business, it
could go bankrupt and shut down overnight.  Likewise I could suddenly
keel over, or something could happen to my network.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Glenn Randers-Pehrson]

On Tue, Mar 10, 2009 at 2:54 AM, Brandon Casey <drafnel@...> wrote:

> On Tue, Mar 10, 2009 at 1:19 AM, Brandon Casey <drafnel@...> wrote:
>
>> Try replacing one of these branch names wherever you see the name 'master'.
>>
>>   git config branch.v12.remote origin
>>   git config branch.v12.merge refs/heads/v12
>>   git push origin v12
>>   etc.
>>
>> You can push all of your branches at one time, once they are all set up.
>>
>>   git push origin v00 v10 v12 v14
>
> I misspoke a little here.  You can push a branch with the above
> command line at any time.  I said ;"...once they are all set up", but
> you don't have to associate a remote with it, or set up the branch for
> merging first.
>
> i.e. you can do this:
>
>   git push origin v00 v10 v12 v14
>
> before you do this
>
>   git config branch.v12.remote origin
>   git config branch.v12.merge refs/heads/v12
>   git config branch.v10.remote origin
>   etc.
>
> -brandon

I succeeded in creating a git repository on SourceForge and pushing everything
to it.  But then when I modified my local repo I fail to push the changes:

shaggy.simplesystems.org> git push origin v12 v14
glennrp@...'s password:
To ssh://glennrp@.../gitroot/libpng
 ! [rejected]        v12 -> v12 (non-fast forward)
 ! [rejected]        v14 -> v14 (non-fast forward)
error: failed to push some refs to
'ssh://glennrp@.../gitroot/libpng'
shaggy.simplesystems.org>

While learning I would just like to remove the repo and start over but git
seems to provide no mechanism to do that.  Locally I can of course
just use "rm -r repo" but SF doesn't provide that kind of access.

I'll try cloning the SF repository and modifying that...

Glenn

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement

[Glenn Randers-Pehrson]

On Fri, Mar 27, 2009 at 10:17 PM, Glenn Randers-Pehrson
<glennrp@...> wrote:

> I'll try cloning the SF repository and modifying that...

Emperor's new clothes situation again.  The "git clone" downloaded 5
Mb of stuff but
I can't navigate it.  "git status" and "git log" show me nothing and
there are no
visible files in the repo (just .git and its subdirectories).

Curiously, the web browser does work fine with the libpng repo on SourceForge.

Glenn

------------------------------------------------------------------------------
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement