Hi Bharat,
currently, I'm not maintaining a fork. I work directly on the code
that I pull.
I may be wrong (I'm not used to git), but I believe it will be harder
to maintain a fork than a set of patches. As I said in a previous
mail, the problem of the backquotes is really blocking for me.
Everytime I will want to merge the fork with the official code, I will
have to check every SQL query because of the backquotes.
So, for now and with my knowledge of git, I'm not interrested in
maintaining a fork. If you had choosed to remove the backquotes from
the code, I would have done it.
But if you think that my understanding of git is wrong, just tell me.
I'm always happy to learn something new.
Greetings.
Le 19 juin 09 à 22:09, Bharat Mediratta a écrit :
> Hi, Romain. This looks interesting. Are you maintaining these
> changes
> in a fork on GitHub? If you do that, then we can very easily pull in
> the changes that you make which we want in the core code, and anybody
> who wants to use Gallery 3 on Postgres can just follow your fork.
> Keeping your fork in sync is very easy (no harder than what you're
> doing
> today) but the sharing aspect is *much* easier.
>
> -Bharat
------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org__[ g a l l e r y - d e v e l ]_________________________
[ list info/archive -->
http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download -->
http://gallery.sf.net ]