[sane-devel] CanoScan LiDE 110

2010-12-09 Thread stef
Le Thursday 09 December 2010 19:58:05 Thomas De Contes, vous avez ?crit : > Le 2 d?c. 2010 ? 20:45, stef a ?crit : > > Le Thursday 02 December 2010 19:25:44 Thomas De Contes, vous avez ?crit : > >> Hi :-) > >> > >> > >> I just buy a CanoScan LiDE 110 > >> http://www.canon.fr/For%5FHome/Product%5F

[sane-devel] git merge question

2010-12-09 Thread stef
Le Thursday 09 December 2010 12:13:41 Julien BLACHE, vous avez ?crit : > stef wrote: > > Hi, > > > I have finished adding support for the LiDE 110 on a branch. If I merge > > > > this branch on master, all the commit history will be preserved and sent > > to the sane-commit mailing list. Is

[sane-devel] CanoScan LiDE 110

2010-12-09 Thread Thomas De Contes
Le 2 d?c. 2010 ? 20:45, stef a ?crit : > Le Thursday 02 December 2010 19:25:44 Thomas De Contes, vous avez ?crit : >> Hi :-) >> >> >> I just buy a CanoScan LiDE 110 >> http://www.canon.fr/For%5FHome/Product%5FFinder/Scanners/Flatbed/canoscan%5 >> Flide%5F110/ >> >> And it is not listed here :

[sane-devel] git merge question

2010-12-09 Thread Julien BLACHE
stef wrote: Hi, > I have finished adding support for the LiDE 110 on a branch. If I merge > this branch on master, all the commit history will be preserved and sent to > the sane-commit mailing list. Is it OK to do like this, or do we prefer to > have one big commit ? In this case how t