[aur-dev] [PATCH] Devs in AUR couldnt see their packages in Community
I created a small patch to fix FS#11561 [1]. Since i'm starting to look at aur code, It would be good to do some tests before commit this patch. -- Hugo [1] http://bugs.archlinux.org/task/11561
On Mon, Sep 22, 2008 at 08:19:23PM -0300, Hugo Doria wrote:
I created a small patch to fix FS#11561 [1]. Since i'm starting to look at aur code, It would be good to do some tests before commit this patch.
-- Hugo
This looks good. Though git-formatted patches are much more preferred and appreciated in the future. Thanks!
On Mon, Sep 22, 2008 at 08:44:51PM -0400, Loui wrote:
On Mon, Sep 22, 2008 at 08:19:23PM -0300, Hugo Doria wrote:
I created a small patch to fix FS#11561 [1]. Since i'm starting to look at aur code, It would be good to do some tests before commit this patch.
-- Hugo
This looks good. Though git-formatted patches are much more preferred and appreciated in the future. Thanks!
Doh. I just realised this isn't based on the testing branch. The code in that area has significantly changed in testing. So it's best to write patches based on testing if possible. That should probably be mentioned in HACKING though it isn't.
On Tue, Sep 23, 2008 at 3:00 AM, Loui <louipc.ist@gmail.com> wrote:
On Mon, Sep 22, 2008 at 08:44:51PM -0400, Loui wrote:
On Mon, Sep 22, 2008 at 08:19:23PM -0300, Hugo Doria wrote:
I created a small patch to fix FS#11561 [1]. Since i'm starting to look at aur code, It would be good to do some tests before commit this patch.
-- Hugo
This looks good. Though git-formatted patches are much more preferred and appreciated in the future. Thanks!
Doh. I just realised this isn't based on the testing branch.
The code in that area has significantly changed in testing. So it's best to write patches based on testing if possible. That should probably be mentioned in HACKING though it isn't.
and where's the testing branch? A. -- Angel Velásquez angvp @ irc.freenode.net Linux Counter: #359909 Arch Linux Trusted User
On Tue, Sep 23, 2008 at 03:20:11AM +0200, =?ISO-8859-1?Q?Angel_Vel=E1squez_ wrote:
On Tue, Sep 23, 2008 at 3:00 AM, Loui <louipc.ist@gmail.com> wrote:
On Mon, Sep 22, 2008 at 08:44:51PM -0400, Loui wrote:
On Mon, Sep 22, 2008 at 08:19:23PM -0300, Hugo Doria wrote:
I created a small patch to fix FS#11561 [1]. Since i'm starting to look at aur code, It would be good to do some tests before commit this patch.
-- Hugo
This looks good. Though git-formatted patches are much more preferred and appreciated in the future. Thanks!
Doh. I just realised this isn't based on the testing branch.
The code in that area has significantly changed in testing. So it's best to write patches based on testing if possible. That should probably be mentioned in HACKING though it isn't.
and where's the testing branch?
It's in the git repository. Check out http://projects.archlinux.org If you don't know how to use git you should visit http://git.or.cz where there's some very helpful documentation. If you have a copy of the git repo just type: git checkout testing And you will see the testing branch.
On Mon, Sep 22, 2008 at 10:25:54PM -0400, Loui wrote:
On Tue, Sep 23, 2008 at 03:20:11AM +0200, =?ISO-8859-1?Q?Angel_Vel=E1squez_ wrote:
On Tue, Sep 23, 2008 at 3:00 AM, Loui <louipc.ist@gmail.com> wrote:
The code in that area has significantly changed in testing. So it's best to write patches based on testing if possible. That should probably be mentioned in HACKING though it isn't.
and where's the testing branch?
It's in the git repository. Check out http://projects.archlinux.org
If you don't know how to use git you should visit http://git.or.cz where there's some very helpful documentation.
If you have a copy of the git repo just type:
git checkout testing
Correction: git checkout origin/testing
On Tue, Sep 23, 2008 at 4:42 AM, Loui <louipc.ist@gmail.com> wrote:
On Mon, Sep 22, 2008 at 10:25:54PM -0400, Loui wrote:
On Tue, Sep 23, 2008 at 03:20:11AM +0200, =?ISO-8859-1?Q?Angel_Vel=E1squez_ wrote:
On Tue, Sep 23, 2008 at 3:00 AM, Loui <louipc.ist@gmail.com> wrote:
The code in that area has significantly changed in testing. So it's best to write patches based on testing if possible. That should probably be mentioned in HACKING though it isn't.
and where's the testing branch?
It's in the git repository. Check out http://projects.archlinux.org
If you don't know how to use git you should visit http://git.or.cz where there's some very helpful documentation.
Thanks
If you have a copy of the git repo just type:
git checkout testing
Correction: git checkout origin/testing
you use git everyday and you failed?... +1 But, according to this tutorial --> http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html You will have to do: $ git branch testing $ git checkout testing Now you confused me, the tutorial that you pointed me first works fine, and in fact now i see that the lines added by Hugo are written. Write this in the tutorials files might be helpful, plus, i am updating some documentation because somethings are missing or somethings are not explained as well should be. Maybe we should do a wiki page with this information. A. -- Angel Velásquez angvp @ irc.freenode.net Linux Counter: #359909 Arch Linux Trusted User
On Tue, Sep 23, 2008 at 05:17:32AM +0200, =?ISO-8859-1?Q?Angel_Vel=E1squez_ wrote:
On Tue, Sep 23, 2008 at 4:42 AM, Loui <louipc.ist@gmail.com> wrote:
Correction: git checkout origin/testing
you use git everyday and you failed?... +1
But, according to this tutorial --> http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
You will have to do:
$ git branch testing $ git checkout testing
Now you confused me, the tutorial that you pointed me first works fine, and in fact now i see that the lines added by Hugo are written.
I actually created a handy local copy of the testing branch so I'm not really looking at the origin/testing branch most of the time. I forgot that other people might not have created that copy. If the tutorial worked then that's all that matters. Hehe.
Write this in the tutorials files might be helpful, plus, i am updating some documentation because somethings are missing or somethings are not explained as well should be.
Maybe the very basic commands can be explained. It wouldn't make sense to go into too much detail about git. There are plenty of resources to learn it elsewhere. We can definitely provide links though.
Maybe we should do a wiki page with this information.
There is a git article here: http://wiki.archlinux.org/index.php/GIT
participants (3)
-
Angel Velásquez
-
Hugo Doria
-
Loui