search for: moy

...ned at obbligato.org (David A. Greene) writes: > Actually git pull can sometimes get you into trouble. Probably git > fetch / git rebase is the better combination for LLVM. I don't get it. Doesn't "git pull --rebase" do exactly a fetch followed by a rebase? -- Matthieu Moy http://www-verimag.imag.fr/~moy/

Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> writes: > greened at obbligato.org (David A. Greene) writes: > >> Actually git pull can sometimes get you into trouble. Probably git >> fetch / git rebase is the better combination for LLVM. > > I don't get it. > > Doesn...

On Wed, Oct 3, 2012 at 10:15 AM, Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> wrote: > Preston Briggs <preston.briggs at gmail.com> writes: >> Think about costs asymptotically; that's what matters. Calls and >> returns require constant time, just like addition and multiplication. > > Constant time, but no...

...chment was scrubbed... Name: 0002-JIT-fix-linkage-of-weak-and-linkonce-symbols.patch Type: text/x-diff Size: 2880 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110315/f74220f3/attachment-0001.patch> -------------- next part -------------- -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...a revised version, git rebase -i and git commit --amend are your friends". 1) should be something people really agree on, and it people want it to be as close as possible to the existing flow. 2) is a matter of personnal choice (advanced Git users won't need to read it). -- Matthieu Moy http://www-verimag.imag.fr/~moy/

Matthieu Moy <Matthieu.Moy at grenoble-inp.fr> writes: > dag at cray.com (David A. Greene) writes: > >> Jason Kim <jasonwkim at google.com> writes: >> >>> I believe git has a similar system for maintaining "branches of patches"  >> >> A pointer/tutor...

Hello ! I'm struggling again against lattice graprhics. ;) I'm trying to produce a conditionnal xyplot with two conditionning factors (let's say A and B). I want the levels of those factors (A1, A2, etc) to show in the margins of the lattice plot, not in the strips between the panels. A1 A2 A3 plot11 plot12 plot13 B1 plot21 plot22 plot23 B2 I managed to remove the

Hi, The link "Broken versions of GCC and other tools" on http://llvm.org/docs/ReleaseNotes.html points to #brokengcc, where it should point to http://llvm.org/docs/GettingStarted.html#brokengcc I guess. -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...wo questions: * What's the rationale for including -fno-rtti in `llvm-config --cxxflags`? Is this a bug? If not, it should be mentionned in the release notes for 2.7. * How can a user (like me) of the LLVM library derive from LLVM classes and use rtti information? Thanks, -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...ar > version numbers are much nicer for that. In the presence of branches, the version number alone doesn't answer this question, because the commit may be more recent than your HEAD, but in another branch. git branch --contains <sha1>, on the other hand, will tell you. -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...ommits > over to your branch (e.g. because it's a release branch). How is that different from SVN? If revision 1234 fixes a bug is some branch, and the last revision in your trunk is 2345, can you tell whether your trunk has this bugfix applied by looking at revision numbers? -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...itory in /tmp/llvm-clone/.git/ Using higher level of URL: http://llvm.org/svn/llvm-project/llvm => http://llvm.org/svn/llvm-project RA layer request failed: Server sent unexpected return value (403 Forbidden) in response to REPORT request for '/svn/llvm-project/!svn/vcc/default' at /home/moy/local/usr/libexec/git-core/git-svn line 5131 (but I'm not really a git-svn expert either) > So, if you'll find a reasonable combination of cmdline options (which > will provide release branches / tags only), then please let us know > and we'll add the branches/tags to the rep...

Thanks, I must have missed these, added. On Apr 22, 2010, at 1:28 AM, Matthieu Moy wrote: > Chris Lattner <clattner at apple.com> writes: > >> Ok, the LLVM 2.7 release notes are in near final shape. Please take >> a look and suggest improvements (or, better yet, just commit >> improvements if you have commit access): > > About the API chang...

...ly rework your history (things like "git rebase -i" are just great for that) to clean it up, and then have it accepted by upstream. Ideally, you make sur the testsuite passes for each commit before pushing. If you like incremental development, you're going to love DVCS. -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...hin what we usually call a "branch" (i.e. the set of commits reachable from the ref) : A --- B \ \ C --- D --- E <--- master Commits B and C will have the same generation numbers. I hardly see a context where they could be used by end users as commit identifiers. -- Matthieu Moy http://www-verimag.imag.fr/~moy/

On Jul 23, 2011, at 4:34 AM, Matthieu Moy wrote: > Chris Lattner <clattner at apple.com> writes: > >> I really do appreciate distributed VCS, but only as staging. >> Incremental development is crucial for the project and "take this git >> push with 100K of code" will never be acceptable. > >...

> What options were used with git-svn init?  It certainly can support > multiple branch/tag directories: > > init >  --tags=<tags_subdir> >  --branches=<branches_subdir> > >  You can specify more than one --tags and/or --branches options, in >  case your Subversion repository places tags or branches under multiple >  paths. The svn repository is free to

...to fit in ReleaseNotes.html: - New argument DisableVerify to llvm::TargetMachine::addPassesToEmitWholeFile (it has a default value, but one must update the declaration of redefinition of this function in derived classes). - TargetAsmInfo changed to MCAsmInfo in back-end writters. -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...again, it won't notice that C1/C2 and C1'/C2' are meant to be the same, and do awkward things instead of a clean merge. So, you may pull from a clone to another, but you cannot alternatively pull from a clone to another and rebase on upstream without getting into trouble. -- Matthieu Moy http://www-verimag.imag.fr/~moy/

...from > the market leader. I don't use submodules enough to be a good juge, but my understanding is that Git's submodules are conceptually nice, but that most people agree that the UI is not good. There's a summer of code on that subject, so there's still hope ;-). -- Matthieu Moy http://www-verimag.imag.fr/~moy/