Re: [FFmpeg-devel] [PATCH] git-howto: mention how to clone ffmpeg-web

[Andreas Cadhalpun]

On 25.11.2015 01:26, Andreas Cadhalpun wrote:
> Subject: [PATCH] git-howto: mention how to clone ffmpeg-web
> 
> Signed-off-by: Andreas Cadhalpun 
> ---
>  doc/git-howto.texi | 15 +++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/doc/git-howto.texi b/doc/git-howto.texi
> index bf37bcc..e5e3c81 100644
> --- a/doc/git-howto.texi
> +++ b/doc/git-howto.texi
> @@ -65,6 +65,21 @@ git clone git@@source.ffmpeg.org:ffmpeg 
>  This will put the FFmpeg sources into the directory @var{} and let
>  you push back your changes to the remote repository.
>  
> +@example
> +git clone gil@@ffmpeg.org:ffmpeg-web 
> +@end example
> +
> +This will put the source of the FFmpeg website into the directory
> +@var{} and let you push back your changes to the remote repository.
> +(Note that @var{gil} stands for GItoLite and is not a typo of @var{git}.)
> +
> +If you don't have write-access to the ffmpeg-web repository, you can
> +create patches after making a read-only ffmpeg-web clone:
> +
> +@example
> +git clone git://ffmpeg.org/ffmpeg-web 
> +@end example
> +
>  Make sure that you do not have Windows line endings in your checkouts,
>  otherwise you may experience spurious compilation failures. One way to
>  achieve this is to run

I pushed this version now.
Feel free to improve it further.

Best regards,
Andreas

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] git-howto: mention how to clone ffmpeg-web

[Andreas Cadhalpun]

Signed-off-by: Andreas Cadhalpun 
---
 doc/git-howto.texi | 8 
 1 file changed, 8 insertions(+)

diff --git a/doc/git-howto.texi b/doc/git-howto.texi
index bf37bcc..88b9926 100644
--- a/doc/git-howto.texi
+++ b/doc/git-howto.texi
@@ -65,6 +65,14 @@ git clone git@@source.ffmpeg.org:ffmpeg 
 This will put the FFmpeg sources into the directory @var{} and let
 you push back your changes to the remote repository.
 
+@example
+git clone gil@@ffmpeg.org:ffmpeg-web 
+@end example
+
+This will put the source of the FFmpeg website into the directory
+@var{} and let you push back your changes to the remote repository.
+(Note that @var{gil} is not a typo of @var{git}.)
+
 Make sure that you do not have Windows line endings in your checkouts,
 otherwise you may experience spurious compilation failures. One way to
 achieve this is to run
-- 
2.6.2
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] git-howto: mention how to clone ffmpeg-web

[compn]

On Wed, 25 Nov 2015 00:55:25 +0100
Andreas Cadhalpun  wrote:


> +@example
> +git clone gil@@ffmpeg.org:ffmpeg-web 
> +@end example
> +
> +This will put the source of the FFmpeg website into the directory
> +@var{} and let you push back your changes to the remote

patch lgtm

but ffmpeg-web repo has iirc limited write-access to only a few
developers currently , so possibly a note should be added about sending
patches? i'm not sure... its up to you.

-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] git-howto: mention how to clone ffmpeg-web

[Andreas Cadhalpun]

On 25.11.2015 01:11, compn wrote:
> On Wed, 25 Nov 2015 00:55:25 +0100
> Andreas Cadhalpun  wrote:
> 
> 
>> +@example
>> +git clone gil@@ffmpeg.org:ffmpeg-web 
>> +@end example
>> +
>> +This will put the source of the FFmpeg website into the directory
>> +@var{} and let you push back your changes to the remote
> 
> patch lgtm
> 
> but ffmpeg-web repo has iirc limited write-access to only a few
> developers currently , so possibly a note should be added about sending
> patches? i'm not sure... its up to you.

I tried to add such a note, see attached patch.

Best regards,
Andreas

>From 423b0f91afdc07965d0b8a47e663afbe2d345fe7 Mon Sep 17 00:00:00 2001
From: Andreas Cadhalpun 
Date: Wed, 25 Nov 2015 00:52:39 +0100
Subject: [PATCH] git-howto: mention how to clone ffmpeg-web

Signed-off-by: Andreas Cadhalpun 
---
 doc/git-howto.texi | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/doc/git-howto.texi b/doc/git-howto.texi
index bf37bcc..e5e3c81 100644
--- a/doc/git-howto.texi
+++ b/doc/git-howto.texi
@@ -65,6 +65,21 @@ git clone git@@source.ffmpeg.org:ffmpeg 
 This will put the FFmpeg sources into the directory @var{} and let
 you push back your changes to the remote repository.
 
+@example
+git clone gil@@ffmpeg.org:ffmpeg-web 
+@end example
+
+This will put the source of the FFmpeg website into the directory
+@var{} and let you push back your changes to the remote repository.
+(Note that @var{gil} stands for GItoLite and is not a typo of @var{git}.)
+
+If you don't have write-access to the ffmpeg-web repository, you can
+create patches after making a read-only ffmpeg-web clone:
+
+@example
+git clone git://ffmpeg.org/ffmpeg-web 
+@end example
+
 Make sure that you do not have Windows line endings in your checkouts,
 otherwise you may experience spurious compilation failures. One way to
 achieve this is to run
-- 
2.6.2

___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel