Re: [arch-dev-public] [arch-commits] CVS update of core/base/filesystem (PKGBUILD filesystem.install)
On Feb 8, 2008 4:55 AM, Pierre Schmitz
Date: Friday, February 8, 2008 @ 05:55:28 Author: pierre Path: /home/cvs-core/core/base/filesystem
Modified: PKGBUILD (1.95 -> 1.96) filesystem.install (1.15 -> 1.16)
upgpkg: filesystem 2007.11-7
Pierre, please notify me before you make changes like this - I have 2 other changes to make on filesystem, in addition to bumping to 2008.02 for the ISO release. This was going to be done tonight (now + 6h) anyway.
Am Freitag, 8. Februar 2008 18:40:50 schrieb Aaron Griffin:
Pierre, please notify me before you make changes like this - I have 2 other changes to make on filesystem, in addition to bumping to 2008.02 for the ISO release. This was going to be done tonight (now + 6h) anyway.
Well, at first: realsing two versions per day would not hurt that much. :-) Perhaps its easier the other way round: If you have some changes on you to-do list, drop a line when you will commit them. This morning I just noticed that the bug was still not fixed and asked the maintainer (brain0) if he would be fine if I just commit this simple change. Pierre -- archlinux.de
On Feb 8, 2008 12:07 PM, Pierre Schmitz
Am Freitag, 8. Februar 2008 18:40:50 schrieb Aaron Griffin:
Pierre, please notify me before you make changes like this - I have 2 other changes to make on filesystem, in addition to bumping to 2008.02 for the ISO release. This was going to be done tonight (now + 6h) anyway.
Well, at first: realsing two versions per day would not hurt that much. :-) Perhaps its easier the other way round: If you have some changes on you to-do list, drop a line when you will commit them.
Are you suggesting I should notify the dev list for every little thing I plan on doing? I could do that, but I have a feeling I'd be spamming the list.
Am Freitag, 8. Februar 2008 19:13:26 schrieb Aaron Griffin:
Are you suggesting I should notify the dev list for every little thing I plan on doing? I could do that, but I have a feeling I'd be spamming the list.
Well, at least let the maintainer know. :-) The other way round: Should I inform every developer when I want to commit some little fix to a package or just ask the maintainer? :-) -- archlinux.de
Am Freitag, 8. Februar 2008 schrieb Pierre Schmitz:
Am Freitag, 8. Februar 2008 19:13:26 schrieb Aaron Griffin:
Are you suggesting I should notify the dev list for every little thing I plan on doing? I could do that, but I have a feeling I'd be spamming the list.
Well, at least let the maintainer know. :-) The other way round: Should I inform every developer when I want to commit some little fix to a package or just ask the maintainer? :-)
ah comeon guys nit picking is not worth on this issue ;) greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Feb 8, 2008 12:19 PM, Pierre Schmitz
Am Freitag, 8. Februar 2008 19:13:26 schrieb Aaron Griffin:
Are you suggesting I should notify the dev list for every little thing I plan on doing? I could do that, but I have a feeling I'd be spamming the list.
Well, at least let the maintainer know. :-) The other way round: Should I inform every developer when I want to commit some little fix to a package or just ask the maintainer? :-)
Well, I guess the issue here is confusing. Because Thomas was inactive for a while, I have all the filesystem bugs assigned to me. So it's no one's fault, I actually thought I was listed as the maintainer because I had all these bugs assigned to me.
Am Freitag, 8. Februar 2008 19:36:18 schrieb Aaron Griffin:
Well, I guess the issue here is confusing. Because Thomas was inactive for a while, I have all the filesystem bugs assigned to me. So it's no one's fault, I actually thought I was listed as the maintainer because I had all these bugs assigned to me.
Never mind. Nobody got hurt. :-) Some day we will have the option to assign multiple maintainers to a package. -- archlinux.de
2008/2/8, Pierre Schmitz
Am Freitag, 8. Februar 2008 19:36:18 schrieb Aaron Griffin:
Well, I guess the issue here is confusing. Because Thomas was inactive for a while, I have all the filesystem bugs assigned to me. So it's no one's fault, I actually thought I was listed as the maintainer because I had all these bugs assigned to me.
Never mind. Nobody got hurt. :-) Some day we will have the option to assign multiple maintainers to a package.
Right now multiple maintainers exist only in my head when assigning multiple devs to some kind of bugreports, :-P but not on dashboard yet. -- Roman Kyrylych (Роман Кирилич)
participants (4)
-
Aaron Griffin
-
Pierre Schmitz
-
Roman Kyrylych
-
Tobias Powalowski