search for: committed

Hi Chris and John, You are listed as administrators for llvm-commits. Can you provide some help in this issue: that my LLVM svn commit messages do not reach llvm-commits? /Patrik Hägglund -----Original Message----- From: llvm-commits-bounces at cs.uiuc.edu [mailto:llvm-commits-bounces at cs.uiuc.edu] On Behalf Of Patrik Hägglund H Sent: den 28 november 2012 22:19 To: Tobias Grosser Cc:

On 11/28/2012 03:47 PM, Jean-Daniel Dupas wrote: > > Le 28 nov. 2012 à 15:07, Tobias Grosser <tobias at grosser.es> a écrit : > >> Hi, >> >> I just realized non of Patrik's commit mails has every reached llvm-commits. Neither my own archive nor the web interface contains commit messages for any of his commits. The relevant commits are >> >> 168785,

...5b8e8f0bed81a28dffb8eba526002f2b3 https://github.com/llvm/llvm-project/commit/24b81434a056825f4e9dd3ef06bad7a2ef34f813 https://github.com/llvm/llvm-project/commit/3191fa21be09d6e7352751f86626a2e8fb251555 This is confusing for everyone, because the Phabricator review gets closed with "this was committed" and the commit can be found on GitHub, but since it's not on any branch, it was really just pushed into the void. The reason I noticed is that the commit emails for those get sent to the llvm-branch-commits list. Is it possible to configure GitHub in some way that disallows pushing comm...

> @Patrik: would you mind to check if you are subscribed with your ericsson email address? As far as I can see, I'm subscribed to llvm-commits with the same email address used in commits (I get buildbot failure emails to the same mail account as llvm-commits messages). (BTW, why should my subscription status to llvm-commits matter?) > It would be nice to see your commit mails. Yes,

On Wed, Dec 18, 2019 at 4:56 AM Peter Waller <Peter.Waller at arm.com> wrote: > On 17/12/2019 22:25, James Y Knight wrote: > > I think it would probably make the most sense to land this as a single > > merge-commit (from the 2700-commit rewritten history you've created) > > onto llvm-project master, rather than as 2700 individual toplevel > > commits to

New branch ''rtmp'' available with the following commits: commit 03292617084fb246a2f23f566d9b5a1afafede41 Author: Benjamin Otte <otte at gnome.org> Date: Sun Dec 14 21:43:56 2008 +0100 split in_error() from is_connected() commit 139261910ef6120f56c6c6749a3843c5dd4af4e4 Author: Benjamin Otte <otte at gnome.org> Date: Sun Dec 14 21:25:50 2008 +0100

Has anyone noticed missing llvm-commits messages? Not all commits seem to generate emails to llvm-commits. For example, I can’t find an email for this commit: https://github.com/llvm/llvm-project/commit/4a6e13ad88ddcc0ab92ace49d4c761921e7f7070 <https://github.com/llvm/llvm-project/commit/4a6e13ad88ddcc0ab92ace49d4c761921e7f7070> Nor does it appear here:

I have made claims that I have not left the compiz project and that I have been maintaining it over the past 4 years, despite the lack of releases by not fault but my own. At the request of some of the original compiz developers, I am now posting a compilation of some of the contributions I've made over time, since the beginning. Since the most important contributions are code and easiest to

.gitignore | 5 Makefile.am | 1 configure.ac | 33 mozilla-sucks/.gitignore | 3 mozilla-sucks/Makefile.am | 14 mozilla-sucks/jni.h | 1810 ++++++++++++++++++++++++++++++++++++ mozilla-sucks/jni_md.h | 182 +++ mozilla-sucks/jri.h | 689 +++++++++++++

On 29.11.2012, at 15:53, Patrik Hägglund H <patrik.h.hagglund at ericsson.com> wrote: > Hi Chris and John, > > You are listed as administrators for llvm-commits. Can you provide some help in this issue: that my LLVM svn commit messages do not reach llvm-commits? My guess: the mailer may have issues with the non-ascii character "ä" in your name. See also

By the way, I've been using the existing read-only monorepo [1] for a few days now. The intent is to commit via the script I put together [2], although I haven't committed anything other than a testing commit [3]. All I can say is, *wow* is it nice. I hid everything I don't care about using a sparse checkout [4]. Many of my tools (e.g. ctrl-p [5] [6], ycm [7]) suddenly work better now that there isn't an artificial boundary between my clang and llvm reposi...

> And if it is, then the "only thing a monorepo gets you" isn't something that you need a monorepo to get. This is an *extremely important* point to understand, so let me try to be really clear about the current state of the world and the state of the world under the two "move to git" proposals. Today, all commits ultimately end up in SVN. Our SVN is a effectively a

I need some clarification on the FOID handed to zil_commit. I wrote a dscript to watch entry and return of zil_commit_writer. Here is an example output: <pre> 2009 Jan 23 23:34:36: ZIL Commit : Seq 183211310 : FOID 129644 Completed in 0 ms 2009 Jan 23 23:34:36: ZIL Commit : Seq 183211324 : FOID 129644 Completed in 0 ms 2009 Jan 23 23:34:36: ZIL Commit : Seq 183211386

Hi Kashyap Chamarthy: thank you very much for answer my question: 一： lead to VM filesystem becoming read-only 1： test case it lead to VM filesystem becoming read-only test case as follows: we want to snapshot for VM , to obtain VM incremental data，and use virsh blockcommit，qemu-img commit，qemu-img rebase to shorten snapshot chain. Details are as follows（when VM running state， we perform the

...eview and discouraged, but seems sometimes necessary when you have dependent commits that are logically separate but need to be reviewed together to make sense. There seems to be a split between those who prefer to curate commits locally and present them in the PR (i.e. Method 3) as they are to be committed (i.e. squash/amend/etc from my workstation and push the result), and those who seem to feel that it is better to avoid "git rebase" and "git commit --amend" and let github handle rewriting the history with the commit. Steve On Wed, Jan 29, 2020 at 12:56 AM Nicolai Hähnle via...

Hi everyone, I recently was granted commit access, but I'm not really sure what is the process. The developer policy states: "You are granted *commit-after-approval* to all parts of LLVM. To get approval, submit a patch <https://llvm.org/docs/DeveloperPolicy.html#patch> to llvm-commits <http://lists.llvm.org/mailman/listinfo/llvm-commits>. When approved, you may commit it

> The only thing a monorepo gets you that strictly isn’t possible without > it is the ability to commit to multiple projects in a single commit. > Personally I don’t think that is a big enough justification, but that is > my opinion, not a fact. Okay, I just bumped into r277008, in which commits to llvm, clang, and clang-tools-extra all have the same SVN revision number. I don't

...5vGaHrUhBKq-Z_9uc/edit?usp=sharing As you can see, the linker is faster than the original. A few key findings are listed below: - The linker tend to be gradually getting slower over time in general. - There are a few commits that increased link time by a few percent or more. - However, we also committed a few performance improvement changes to offset them. The commit that increased link time most (+15%) is r251212: Add support for merging string from SHF_STRINGS sections. This does not come as a surprise since string merging is a computationally heavy operation. The commit that decreased link ti...

Hi, I just realized non of Patrik's commit mails has every reached llvm-commits. Neither my own archive nor the web interface contains commit messages for any of his commits. The relevant commits are 168785, 168516, 168507, 167924, 157381, 157323, 157320, 157319, 157184 Does anybody have any idea why those commit mails would get lost? Or did I just overlook something? Cheers Tobi

New branch 'linear' available with the following commits: commit 37812ef682f70d5166ecdce48523d86495efdc84 Author: Benjamin Otte <otte at gnome.org> Date: Mon Jan 14 20:15:13 2008 +0100 whoops, typo commit 6b93b528ca25ac23cb6758611aae1009f46b2ae3 Author: Benjamin Otte <otte at gnome.org> Date: Mon Jan 14 20:13:53 2008 +0100 catch a loader error, too commit